I have the following DNS but it is not pointing correctly.
What I have is one website that checks the url and pulls info from the DB based on the URL.
I have about 50 domains pointed to the same ip but only one website actually on the IP... hope that makes sense.
It was all working great until I changed the default website for that IP to another page that I am testing, it broke all of the other pages. I thought it would be fine since the cname is pointed to the main website, but it did not work.
Can you please let me know how to resolve this.
austinminisearch.com
NS
Subdomain Name Server TTL Actions
ns1.codero.com. 14400
ns2.codero.com. 14400
MX
There are currently no MX resource records
A
Name IP Address TTL Actions
@ 69.64.82.57 14400
mail 69.64.82.57 14400
AAAA
There are currently no AAAA resource records
CNAME
Alias Hostname TTL Actions
makemodelsearch.com. 14400
There are currently no TXT resource records
There are currently no SRV resource records
I would not expect it to be reliable. It breaks the ANY response DNS clients get back because address records are not returned.
However, I don't think that's the cause of your problem (red flags, sirens, all that kind of thing, but likely to be unrelated).
I would hypothesise that the page you've changed was the one answering on any name? The one you have left only answers when makemodelsearch.com is in the host header?
DNS will not change the name used to access a resource (it is not responsible for URL rewriting). Therefore if a user enters http://austinminisearch.com the web server must be prepared to answer a request for that name, even if your content is drawn from something you refer to as makemodelsearch.com.
Any good?
Chris
arnold
As chris pointed out, a CNAME for the domain name itself is a problem, The impact will be only on mail handling, and since you do not have it setup, it does not really matter. I suspect, that your domain registrar/dns console provide might actually
The other issue is that URL are often prepended with www.domainname.com which in your case does not exist nor is the cname.
Your other issue deals with the conflict of
Host entry
@ IPaddress
CNAME
Something redirects requests that are not makemodelsearch.com to the raw IP address, where the defasult web site kicks in. It is either a rewrite in Apache httpd.conf or a piece of code in the default page.
You have Plesk which is the main suspect and where I would start my troubleshooting efforts.
Open in new window
I would not expect it to be reliable. It breaks the ANY response DNS clients get back because address records are not returned.However, I don't think that's the cause of your problem (red flags, sirens, all that kind of thing, but likely to be unrelated).
I would hypothesise that the page you've changed was the one answering on any name? The one you have left only answers when makemodelsearch.com is in the host header?
DNS will not change the name used to access a resource (it is not responsible for URL rewriting). Therefore if a user enters http://austinminisearch.com the web server must be prepared to answer a request for that name, even if your content is drawn from something you refer to as makemodelsearch.com.
Any good?
Chris