It has nothing to do with individual domains, it has to do with the nameservers they are pointed at.
All of a sudden domains not resolving
- Thread starter Rage9
- Start date
It has nothing to do with individual domains, it has to do with the nameservers they are pointed at.
Right -- so with this is mind what do you check to know whether or not you are safe? If your nameservers have A records for themselves in them? What else is there?
I hate to bump this thread, but this issue just snuck up on me again. This time instead of changing the DNS records with the registrar to the host's default (removing private nameservers) I decided to crack open WHM and give it a your way a try (updating a records).
Could someone please check the below screenshot and verify for me that the page ( WHM > Edit DNS Zone ) is the only thing I have to do in order to update this site.
The "a" column was set to the right IP address but the NS select box had the host's default DNS. I changed that to dns1.domain.com (does capitalization matter?) and the one below it to dns2. Also everything defaults with a period (.) after it ... looked odd but nothing I could do about that.
Someone with supreme DNS knowledge could really make my life easier here. The difference between stats (202 & custom) and adwords is about 10-20% consistantly and I've got 2 people confirming yesterday that their browsers had the site as down ... one of them said they could go through a proxy and get it.
thanks in advance
edit: intodns.com now shows that my "Nameservers A records are good" but I still have a few warnings (Different subnets, Different autonomous systems, SOA MNAME entry, SOA EXPIRE) and an error (Reverse MX A records (PTR)).
FUCK THIS NOISE ... why is dns shit such an unknown to me???
Could someone please check the below screenshot and verify for me that the page ( WHM > Edit DNS Zone ) is the only thing I have to do in order to update this site.
The "a" column was set to the right IP address but the NS select box had the host's default DNS. I changed that to dns1.domain.com (does capitalization matter?) and the one below it to dns2. Also everything defaults with a period (.) after it ... looked odd but nothing I could do about that.
Someone with supreme DNS knowledge could really make my life easier here. The difference between stats (202 & custom) and adwords is about 10-20% consistantly and I've got 2 people confirming yesterday that their browsers had the site as down ... one of them said they could go through a proxy and get it.
thanks in advance
edit: intodns.com now shows that my "Nameservers A records are good" but I still have a few warnings (Different subnets, Different autonomous systems, SOA MNAME entry, SOA EXPIRE) and an error (Reverse MX A records (PTR)).
FUCK THIS NOISE ... why is dns shit such an unknown to me???
Attachments
At the very least, under where the photo is cut off on the bottom you need to add the following:
A records:
mydomain.com. 14400 IN A your.hosted.IP.address
localhost 14400 IN A 127.0.0.1
www 14400 IN A your.hosted.IP.address
Yes, that's a trailing dot after "com" on the first record and not the rest.
A records:
mydomain.com. 14400 IN A your.hosted.IP.address
localhost 14400 IN A 127.0.0.1
www 14400 IN A your.hosted.IP.address
Yes, that's a trailing dot after "com" on the first record and not the rest.