Google Public DNS not resolving subdomain...

[Rick From Jersey]

A subdomain on one of my .com is not resolving properly while I'm using Google Public DNS. Here's what I did to setup the subdomain.

I logged into my domain registrar account and then went into my Dashboard, I went down to the DNS records and click on Add New Record then under Advance DNS I selected "URL Redirect Record", under Host I entered the subdomain name, then under Value is the URL address that I am forwarding to and the TTL is set to 30, I then clicked Saved All Changes and then logout completely. I then went into the Chrome Browser and cleared all history and cookies, closed the browser and opened the DOS command prompt and flushed all of the DNS records from my cache using IPCONFIG /flushdns.

I did a periodical check and found that while I'm using 8.8.8.8 and 8.8.4.4 as my DNS servers in my router even after 45 minutes to 1 hour the subdomain had not yet resolved and I kept getting a 404 Page Not Found error but when I reverted the router to my ISP's DNS servers the subdomains worked fine, I even used my smartphone and iPad both of which have separate ISPs and the computers in the library in my community which are are on the Homeowners Association's corporate servers the subdomain worked fine but when I go back to 8.8.8.8 / 8.8.4.4 that's when the problem's ugly face pops up again.

Oh and I forgot to mention the main page of my domain works fine because it points to my Blogger page using the CNAME records ghs.google.com and (redacted).googlehosted.com so it's appears that its an issues with recognizing and resolving my subdomains on Google Public DNS. Help would be appreciated.

[Alex Dupuy]

Hi Rick,

You have included a lot of information, but left out the most important one, which is the name of the domain that isn't being resolved properly. 

You wrote:

I logged into my domain registrar account and then went into my Dashboard, I went down to the DNS records and click on Add New Record then under Advance DNS I selected "URL Redirect Record", under Host I entered the subdomain name, then under Value is the URL address that I am forwarding to and the TTL is set to 30

Note that although many registrars offer a URL Redirect feature, this is not something that is part of DNS. URL Redirects are HTTP features, so they are implemented by providing a DNS 'A' (address) or CNAME (alias) record for the subdomain that points to a stub web server run by the registry that returns the HTTP redirect.

 

I then went into the Chrome Browser and cleared all history and cookies, closed the browser and opened the DOS command prompt and flushed all of the DNS records from my cache using IPCONFIG /flushdns.

Note that this flushes only your local DNS cache – it does not flush the caches for any resolvers by other parties. You can flush Google Public DNS records, and some other public DNS services have similar features. However, if your problem is related to stale cache data, that data expired days ago.

Oh and I forgot to mention the main page of my domain works fine because it points to my Blogger page using the CNAME records ghs.google.com and (redacted).googlehosted.com so it's appears that its an issues with recognizing and resolving my subdomains on Google Public DNS. Help would be appreciated.

If you're still having the problem, and it wasn't just cached data, please provide the specific subdomain.