NS Records Not Updating After Several Days Despite Correct Configuration
I have a server with the address server.mydomain.com, but the NS records for the domain are not being set even after several days. Below is the list of actions I have taken. Is there anything else I might have forgotten?
- I have created A records with the server's IP for ns7.mydomain.com and ns8.mydomain.com in Cloudflare.
- I have created ChildHost for ns7.mydomain.com and ns8.mydomain.com in my domain panel.
- I have created an A record with the server's IP for the hostname.
- I have added the NS records in the Basic WebHost Manager® Setup section and used the Configure Address Records option to add the server's IP for each NS.
- In the zone editor for the domain in question (rahebomeh.ir), everything appears to be correct. (NS,A,CNAME,...)
However, if you check https://dnschecker.org/#NS/rahebimeh.ir, even after more than 10 days, the NS records are not being set.
-
Did you create glue records at your registrar? At the registrar you have to register those nameservers. Google DNS glue records or nameserver glue records . Without glue records, you'll have issues.
0 -
mtindor Do you mean setting up glue records for the domain rahebimeh.ir? Because in the hostname of my .com domain server, there is something named childhost that has been added.
However, for the .ir domain, my registrar has given the message that it is not possible to add glue records:
Glue record requirement: You need to enter the server IP address only if the introduced domain name server is dependent on the same domain name. For example, if you want to define two domain name servers for the domain example.ir with the names ns1.example.ir and ns2.example.ir, then entering the IP for these two name servers will be necessary. In other cases, it is not necessary and will be ignored.0 -
You need to add glue records at the registrar for:
ns7.mydomain.com
ns8.mydomain.com
So if your domain is blahblahhosting.com and you want to set up ns1.blahblahhosting.com and ns2.blahblahhosting.com
Then go to the registrar where blahblahhosting.com is purchased and add glue records for ns1/ns2 that map them to the proper IP addresses.
0 -
You also need to make sure that DNS (named) is up and running (and TCP/UDP 53 open inbound) for the server where ns7 and ns8 are, so that external DNS servers can query and get a response from ns7 and ns8.
0 -
Clue: you do not have your DNS (named) running on the ns7/ns8 box, OR you do not have the TCP/UDP 53 ports open so the outside world can query them. So nobody can query records for the domain in question.
0 -
mtindor When I enable
namedusing the commandsystemctl enable named, it activates successfully. However, after two minutes, it goes back to a failed state.[root@irserver2 ~]# systemctl status named
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/named.service.d
└─cpanel.conf
Active: failed (Result: exit-code) since Wed 2024-06-26 12:17:46 +0330; 7min ago
Process: 1690616 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=1/FAILURE)
Process: 1690354 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS (code=exited, status=0/SUCCESS)
Process: 1690350 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF">
Main PID: 1690355 (code=exited, status=0/SUCCESS)0 -
Sorry. I can't help you there. No idea why it would do that.
in WHM, under Service Manager, you should make sure that next to "DNS Server" you have both Enable and Monitor checkmarked.. and save that.
Might have to look in /var/log/messages for more clues. If Named starts at all, there will be some logging to a file - and by default its probably /var/log/messages. And when it stops, same thing.
I don't use Ubuntu, so i'm not familiar with where the logging would be. But you'd need to look at that.
0
Please sign in to leave a comment.
Comments
7 comments