CentOS: DNS named giving out random timeouts?
Hi All,
I have a VPS running DNS (named). If i telnet to the server frommy hose and run a query i get an authorative response with the correct IP. I've tried the exact same test from four other locaction, three timeout and one works.
Any suggestions on how to fix it. As quite a lot of users are unable to access my server.
many thanks
D
I have a VPS running DNS (named). If i telnet to the server frommy hose and run a query i get an authorative response with the correct IP. I've tried the exact same test from four other locaction, three timeout and one works.
Any suggestions on how to fix it. As quite a lot of users are unable to access my server.
many thanks
D
Papertrip
What is one of the domains you are having trouble resolving?
ASKER
everything is working again.
very bizarre.
very bizarre.
ASKER
Any idea what could have caused this?
I sent an email to the support team to see if any network changes were made. So maybe they fixed it.
I sent an email to the support team to see if any network changes were made. So maybe they fixed it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the info.
There's nothing fancy with the server. Hopefully the host will come back and say what the changed.
I had a quick look at zoneedit and the charge for secondary dns. "Please note that free zones do not include tertiary nameservice or other premium services."
There's nothing fancy with the server. Hopefully the host will come back and say what the changed.
I had a quick look at zoneedit and the charge for secondary dns. "Please note that free zones do not include tertiary nameservice or other premium services."
Ah ya know I remember zoneedit from long ago but I must admit they could have changed their model since then.
IMO just google "free secondary dns", I just did and there are a TON more than when I looked long ago...
IMO just google "free secondary dns", I just did and there are a TON more than when I looked long ago...
> Aside from that, you are testing ingress and I can't imagine a DNS query coming anywhere close to 1400 bytes.
It is not about packet size approaching 1400 byte. IT is about the DNS servers are placed in an network segment having packet fragmentation issues. 1400 byte packages are just to display there's a problem (fragmented packets can not be assembled later). With these type of packets you wouldn't know at what point you will have an issue when communicating from different networks not just 1400+ byte packets from where
Cheers,
K.
It is not about packet size approaching 1400 byte. IT is about the DNS servers are placed in an network segment having packet fragmentation issues. 1400 byte packages are just to display there's a problem (fragmented packets can not be assembled later). With these type of packets you wouldn't know at what point you will have an issue when communicating from different networks not just 1400+ byte packets from where
Cheers,
K.
ASKER
The host came back to me to say there was a BGP upstream issue. Apparently someone was having issues but didn't know. They said they were able to remove the vendor from their BGP list after my email and have listed in on their outage page.
I guess these things happen.
I guess these things happen.