Member Avatar for thewiredman

Hi everybody:

I want to ask you a question about a problem that I have,
My friend has a VDS godaddy server and a domain name registered under verio-hosting.com

The problem is that verio-hosting is not resolving the domain properly,

Here is the way I set up the dns zones in verio hosting:
Auth Nameservers:

In DNS ZONE:
mydomain.com. 1800 IN NS ns1.mydomain.com.
mydomain.com. 1800 IN NS ns2.mydomain.com.
www.mydomain.com. 86400 IN A IP0-godaddy.assigned
webmail.mydomain.com. 86400 IN A IP0-godaddy.assigned
smtp.mydomain.com. 86400 IN A IP0-godaddy.assigned
ns2.mydomain.com. 1800 IN A IP2-godaddy.assigned
ns1.mydomain.com. 1800 IN A IP1-godaddy.assigned
ftp.mydomain.com. 86400 IN A IP0-godaddy.assigned
mydomain.com. 86400 IN A IP0-godaddy.assigned

See that I'm pointing the NS1, NS2 to the ip1 and ip2 from godaddy.

And in WHM at Godaddy I have :
In Basic WHM/SETUP with IP assigned in Nameservers IP:
Nameserver 1 : ns1.mydomain.com. => IP1-godaddy.assigned
Nameserver 2 : ns2.mydomain.com. => IP2-godaddy.assigned

In mydomain.com ZoneFile:

Cpanel::ZoneFile::VERSION:1.2 mtime:123456444 hostname:
; Zone file for mydomain.com
$TTL 14400
mydomain.com. 86400 IN SOA ns1.mydomain.com. user.mail.com. (
2009061003 ;Serial Number
86400 ;refresh
7200 ;retry
3600000 ;expire
86400 ;minimum
)
mydomain.com. 86400 IN NS ns1.mydomain.com.
mydomain.com. 86400 IN NS ns2.mydomain.com.
mydomain.com. 14400 IN A IP0-godaddy.assigned
localhost 14400 IN A 127.0.0.1
mydomain.com. 14400 IN MX 0 mydomain.com.
www 14400 IN CNAME mydomain.com.
whm 14400 IN A IP0-godaddy.assigned


Am i doing something wrong? Please, I'd appreciate your help very much.
Thanks in advance

  • 3 Contributors
  • 2 Replies
  • 234 Views
  • 12 Hours Discussion Span
  • Latest Post Latest Post by sknake

Dani AI

Generated

Short diagnosis: this is a delegation problem — the parent (the registrar) is still delegating the domain to its current authoritative nameservers while the GoDaddy box has been configured to act as the domain's DNS. NS records placed inside a zone do not change the parent delegation. That mismatch explains why the domain “does not resolve properly” even though WHM on the GoDaddy server shows the custom nameservers and the zone on the server contains the records. has set the server-side zone and WHM nameservers, but the registrar-side delegation must be updated too.

Two practical fixes:

  • Keep registrar DNS authoritative (simpler): leave the registrar/Verio nameservers as the domain's delegation and add or edit A/CNAME/MX records there to point services to the GoDaddy IP(s). No glue or child nameservers required.
  • Make the GoDaddy host authoritative: at the registrar create host/child nameserver entries (commonly called “register nameserver” or “create host” / glue records) that map ns1/domain and ns2/domain to the GoDaddy IPs, then change the domain’s nameservers at the registrar to those child hosts. Ensure WHM is serving DNS, the zone on the server lists the same NS hosts, both ns A records exist, and UDP/TCP port 53 is reachable.

Quick checks to run (replace example.com with the real domain):

whois example.com
dig +trace example.com
dig NS example.com
dig @ns1.example.com example.com SOA

Interpretation: whois shows registrar-listed nameservers; dig +trace shows where delegation stops; querying @ns1.example.com tests whether that server actually serves the zone.

Extra notes: allow DNS propagation (TTL) after changes, verify firewall/ISP blocks aren’t dropping port 53, ensure two distinct nameserver IPs for resilience, and configure reverse DNS on the IPs if mail deliverability matters. ’s point is valid — running custom nameservers adds operational overhead; using the registrar DNS is often the easiest route. As suggested, publishing the actual domain and intended IPs lets helpers verify glue/parent records and give a definitive next step.

Recommended Answers

All 2 Replies

Member Avatar for ithelp

Why do you need auth nameserver ? is verio host tech support not helping ?

Member Avatar for sknake

Please post the real DNS host entries so we can help. When I research DNS I start by looking at the glue records which I cannot do without the domain name and the intended IP you want.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.