You paid for hosting, the welcome email arrived, and the dashboard shows a server waiting for traffic — but typing your domain still opens the old site, a parking page, or nothing at all. That gap is almost always DNS: the domain name still points somewhere else. This guide is for the moment after purchase when you want to change nameservers in Pakistan (or update records at another DNS provider) so your registered domain actually loads your PK Hosting account.
It assumes the name is already yours. Registering or transferring a .pk or .com.pk is a separate PKNIC/registry step — see our beginner's guide to .pk domains and the PK domain registration page. Here we only connect an existing domain to hosting you bought on pricing or checkout.
What nameservers are (without the textbook version)
Your domain is the sign on the shop door; hosting is the shop itself. Nameservers are the directory that tells browsers and mail servers where to find the shop when someone types the name. When you set nameservers to PK Hosting, you are saying: “ask PK Hosting for the IP address, mail records, and anything else this domain needs.”
You can also leave nameservers at another company (Cloudflare, your registrar, an old host) and publish only the records that matter — usually an A record for the root and www, or a CNAME where the panel allows it. Both patterns work; the right one depends on whether you want PK Hosting to manage all DNS or just host the website.
PK Hosting nameservers — use these exact values
When PK Hosting should manage DNS for the domain, set exactly:
- ns1.pkhosting.com
- ns2.pkhosting.com
Do not leave OpenProvider, PKNIC, or a previous host’s default nameservers in place if you expect the dashboard DNS editor and automatic mail/SSL helpers to work against our zone. If you registered elsewhere, you change these at that registrar; if the domain is on your PK Hosting account, use Dashboard → Domains → Manage → Nameservers (wording may vary slightly by service type).
Where you change nameservers
“Point domain to hosting Pakistan” searches usually land here because the button lives in different places depending on who sold the name:
- Domain registered with PK Hosting — open the domain in the client area and update nameservers there, or follow the connect-domain wizard on your hosting service page after the name is linked to the account.
- Global gTLD (.com, .net, etc.) at another registrar — log into that registrar’s control panel, find DNS or nameserver settings, replace the current pair with ns1.pkhosting.com and ns2.pkhosting.com, and save. Many international names route through OpenProvider on our side once registered here; if you bought elsewhere, only that registrar’s panel can push the change upstream.
- .pk / .com.pk registered through PKNIC rules — the same two nameservers apply. PKNIC still expects accurate registrant data (Organization can be a person’s full name for typical business names). Changing nameservers does not re-register the domain; it only updates routing. If WHOIS/RDAP still shows the old host after you save, wait for propagation or confirm you edited the live registrar login, not a stale reseller bookmark.
Not sure who controls DNS today? Run a WHOIS lookup — our free WHOIS tool shows the current nameserver list. That tells you where to log in before you change anything.
Step-by-step: nameserver path (most PK Hosting customers)
- Confirm hosting is active. Billing should show the invoice paid and the hosting service provisioned. Pointing DNS at an empty account wastes time — if you still need a plan, compare tiers on /pricing/ or pay a PKR invoice (JazzCash and EasyPaisa work the same as any hosting bill; see paying with JazzCash or EasyPaisa).
- Copy the two nameservers — ns1.pkhosting.com and ns2.pkhosting.com — into a note so you paste them consistently.
- At the registrar, remove or replace the old nameserver pair. Some panels want two fields; others accept a list. Save and accept any confirmation email.
- Wait for propagation (next section). Do not re-save the same values every hour; that can extend confusion without speeding up the internet.
- On PK Hosting, open your hosting service, run the domain connect / DNS check if offered, issue or renew free SSL once the domain resolves here, and install WordPress or upload files as needed.
If you are migrating from another host rather than launching fresh, read moving without downtime first — email MX records move with nameserver changes, so recreate mailboxes before you cut over. Our free migration team can handle the sequence if you prefer not to touch DNS alone.
How long propagation takes
DNS is cached worldwide. After you save new nameservers, some visitors see the change in minutes; others take up to 48 hours, especially if the old TTL was high or resolvers still hold the previous NS set. Lowering TTL a day ahead helps when you know a cutover is coming — the migration guide above explains that trick.
Propagation is not the same as “PK Hosting activated my account.” Payment confirmation and DNS are separate clocks. Once nameservers show our pair in public lookups, the hosting side can complete SSL validation and serve pages.
How to verify nameservers actually changed
Pick any method that shows what the public internet sees, not just what your browser cached:
- WHOIS / RDAP — check the Nameserver fields for ns1.pkhosting.com and ns2.pkhosting.com. Our WHOIS lookup is enough for a quick read.
- dig or nslookup — from a terminal, query NS records for your domain (
dig NS yourdomain.com +shorton Linux/macOS, ornslookup -type=NS yourdomain.comon Windows). You want our two hosts in the answer. - Online DNS checker — any reputable “DNS propagation checker” that queries multiple global resolvers helps when your home ISP still shows the old data but London or Singapore already sees the new NS.
If WHOIS already lists our nameservers but the site does not load, the problem is usually records inside the zone (missing A record, wrong IP, or SSL not issued yet) — not another nameserver save.
Cloudflare and other external DNS — do not blindly swap NS
If the domain already uses Cloudflare (nameservers like *.ns.cloudflare.com) and the orange-cloud proxy is enabled, changing nameservers to PK Hosting is optional, not mandatory. Many teams keep Cloudflare for CDN and firewall rules and only update records:
- Leave Cloudflare nameservers as they are.
- In Cloudflare DNS, set the A record for
@(and usuallywww) to the IPv4 address shown on your PK Hosting service page, or use the CNAME / hostname the panel lists if that is the documented path. - For proxied records (orange cloud), traffic hits Cloudflare first, then your hosting. That is fine when the IP or target hostname is correct.
- At the root, some setups use CNAME flattening instead of a bare A record — follow whichever record type Cloudflare accepts for your zone without breaking mail.
Switch to ns1.pkhosting.com and ns2.pkhosting.com when you want PK Hosting to host the full DNS zone (web, MX, TXT for verification) in one dashboard. That is simpler for many small businesses; Cloudflare-first is valid when you already depend on their proxy. The dashboard connect wizard and knowledge base nameserver article describe both paths without treating Cloudflare as an error state.
The same logic applies to any external DNS host — only the login URL changes.
After DNS points here: SSL, WordPress, and email
Once the domain resolves to your hosting service:
- SSL — eligible shared and WordPress plans include a free DV certificate. Issue it from the hosting security/SSL section after DNS is live; Let's Encrypt must reach your site on this server. Details sit in the knowledge base SSL article if the first attempt fails.
- WordPress — use one-click install from the control panel on the connected domain. For choosing a tier first, see WordPress hosting in Pakistan: what matters.
- Email — if nameservers moved to PK Hosting, recreate MX and mailbox records (or use the default mail routing the panel suggests). If you kept external DNS, update MX there before you tell staff to send from
you@yourdomain.pk. Our business email guide walks through the order.
Choosing between .pk and .com.pk for a second brand domain? That decision is registration-time, not DNS-time — .pk vs .com.pk compares the extensions without repeating PKNIC signup steps here.
Common mistakes
- Editing DNS at PK Hosting while nameservers still point at the old registrar — changes here have no effect until NS delegates to us.
- Changing nameservers before copying email MX records — mail bounces to the wrong place. Fix records first or move NS only after mailboxes exist on the new host.
- Using a third-party parking or “free website” IP from an old trial — always take the IP/hostname from the live hosting service page.
- Expecting instant SSL before DNS resolves — certificate validation follows routing, not the other way around.
Soft next step
When nameservers are set and propagation looks good, finish setup in the dashboard: SSL, WordPress or site files, then mail. If the domain is not on your account yet, search or transfer from /domains/. Questions about a stuck registrar login or a Cloudflare-only setup? Email support@pkhosting.com or call (042) 35692952 — include the domain name and a WHOIS screenshot of the current nameserver list so support can see what the registry publishes.
