DNS Propagation problem

[Galanthus]

Hello,

I have a simple problem. After upgrading my cpanel and changing my hostname my nameservers stopped working.
Before doing this everything was working very good. When i check the DNS propagation status everythins is good.

When i dig my account i get the correct info.

See: dig shokunin.pro

It is almost 48 hours ago.. but still not working is this normal can somebody check this please?

 

[vanessa]

Seems fine to me, probably an issue with your ISP's DNS cache:

nessa@nessa-desktop:~$ ping shokunin.pro
PING shokunin.pro (149.210.168.31) 56(84) bytes of data.
64 bytes from 149-210-168-31.colo.transip.net (149.210.168.31): icmp_req=1 ttl=51 time=96.8 ms
64 bytes from 149-210-168-31.colo.transip.net (149.210.168.31): icmp_req=2 ttl=51 time=96.5 ms
64 bytes from 149-210-168-31.colo.transip.net (149.210.168.31): icmp_req=3 ttl=51 time=97.1 ms

nessa@nessa-desktop:~$ dig +short shokunin.pro
149.210.168.31



Is that the right IP?

 

[cPanelMichael]

Hello

Try using the dig command with @localhost from your server's command line to see if you get the correct results.

Thank you.

 

[Galanthus]

Seems fine to me, probably an issue with your ISP's DNS cache:

nessa@nessa-desktop:~$ ping shokunin.pro
PING shokunin.pro (149.210.168.31) 56(84) bytes of data.
64 bytes from 149-210-168-31.colo.transip.net (149.210.168.31): icmp_req=1 ttl=51 time=96.8 ms
64 bytes from 149-210-168-31.colo.transip.net (149.210.168.31): icmp_req=2 ttl=51 time=96.5 ms
64 bytes from 149-210-168-31.colo.transip.net (149.210.168.31): icmp_req=3 ttl=51 time=97.1 ms

nessa@nessa-desktop:~$ dig +short shokunin.pro
149.210.168.31



Is that the right IP?

Hi Vanessa! Thanks for the reply. Yes this is my main IP address i am using 2. What do you think do i have to wait.. and what did cause my DNS nameservers not to work out of sudden?

- - - Updated - - -

Hello

Try using the dig command with @localhost from your server's command line to see if you get the correct results.

Thank you.

Yes, when i do with root from SSH dig shokunin.pro i get correct nameservers.. anyhow DNS is giving me errors.. for almost then 48 hours.

 

[cPanelMichael]

Try rebuilding your DNS configuration file via:

/scripts/rebuilddnsconfig

Also, restart the "Named" service and make sure you have no firewall rules that might block access to DNS traffic.

Thank you.

 

[Galanthus]

Try rebuilding your DNS configuration file via:

/scripts/rebuilddnsconfig

Also, restart the "Named" service and make sure you have no firewall rules that might block access to DNS traffic.

Thank you.

Oke, i have rebuild the DNS config and restarted the nameservers. Will this result in another 48 hours of propagation?

 

[vanessa]

I don't see a second IP configured. When I query your nameservers directly, only one IP comes up:

nessa@nessa-desktop:~$ dig +short @ns1.shokunin.pro shokunin.pro
149.210.168.31

So you might want to check the zone to make sure. What it seems like you should have is two A-records, each to one IP. If that's what you're trying to do.

 

[Galanthus]

I don't see a second IP configured. When I query your nameservers directly, only one IP comes up:

nessa@nessa-desktop:~$ dig +short @ns1.shokunin.pro shokunin.pro
149.210.168.31

So you might want to check the zone to make sure. What it seems like you should have is two A-records, each to one IP. If that's what you're trying to do.

Hello Vanessa,

I dont think this is the problem because it was working before the update also. Take a look at my screenshot i do have two A records and two NS records for each IP address. When checking dig shokunin.pro and both ns nameservers i will get the correct it. I have also checked dnsstuff.com for errorss no errors at all.

Is there any way to speedup the dns propagation or test if the nameserver do work?

 

[vanessa]

You don't speed up DNS propagation. DNS propagation refers to how long it takes other nameservers across the internet to update their own records, which is something you don't have control over. Lowering your TTLs before making the change helps.


I only see one A-record for shokunin.pro. So it's likely perhaps the issue you're having was not explained very well. You indicated that shokunin.pro has two IP addresses and you are only seeing one. There is only one IP setup.

To query your namservers directly, use the same command I did above (dig @ns1.shokunin.pro shokunin.pro). If you still need help, please clarify exactly what it is you are trying to do.