nameserver point to site

[benzema]

Hi,

I think I have a problem with my server configuration. I just noticed that I could access my site by visiting ns2.domain.com . This has caused a problem with Google's indexing as it would create duplicate content problems.

I fixed this temporarily by redirecting with .htaccess but I assume this needs a better solution.

Can anyone tell me what to check?

 

[benzema]

update

Can this be related to this?

ns1 A 7x.xxx.xx.96
ns1.domain.com. A 7x.xxx.xx.96
ns2 A 7x.xxx.xx.121
ns2.domain.com. A 7x.xxx.xx.121

 

[SeLLeRoNe]

Provide real domain.

If you can access your www domain using ns1 and ns2 and whatever. so you got a wildcard somewhere in virtual host (like *.domain.com).

Regards

 

[benzema]

Provide real domain.

If you can access your www domain using ns1 and ns2 and whatever. so you got a wildcard somewhere in virtual host (like *.domain.com).

Regards

Thanks for the answer! It was helpful.

I have checked httpd.conf and vhosts, no problem with wildcards. The problem turned out to be the lack of addinitial IP addresses. We have 2 IP addresses and both of them are used by the nameservers. At the same time, the 2nd IP is also the domain IP. I will get additional IP addresses from dc tomorrow and set the 2nd DNS to the new IP address. I will also add another nameserver as I read it's suggested to have at least 3 nameservers.

thanks again, appreciate it.

 

[nobaloney]

I have checked httpd.conf and vhosts, no problem with wildcards. The problem turned out to be the lack of addinitial IP addresses. We have 2 IP addresses and both of them are used by the nameservers. At the same time, the 2nd IP is also the domain IP.

This should be true only if the IP# is assigned to your username directly and not shared. I* believe you should be able to fix this by sharing the IP#.

I will get additional IP addresses from dc tomorrow and set the 2nd DNS to the new IP address. I will also add another nameserver as I read it's suggested to have at least 3 nameservers.

If all nameserver IP#s point to the same machine then there's no advantage at all to having multiple nameservers.

Jeff

 

[benzema]

If all nameserver IP#s point to the same machine then there's no advantage at all to having multiple nameservers.

Jeff

Thanks for mentioning that. I guess this is something I have done without really thinking about it for years. (And I am sure I am not the only one)

the IP# is indeed assigned to my username directly and tagged as "owned" in directadmin IP list. Wouldn't it be easier if set the 2nd name server to another IP?

 

[nobaloney]

Sure; set it for any IP# you want, as long as it's on your server. But it's still not going to be robust DNS because if one IP# fails, the other one will, too. Lots of discussions on this forum on how to create robust DNS; they all require having it hosted in multiple locations.

Jeff

 

[benzema]

Sure; set it for any IP# you want, as long as it's on your server. But it's still not going to be robust DNS because if one IP# fails, the other one will, too. Lots of discussions on this forum on how to create robust DNS; they all require having it hosted in multiple locations.

Jeff

I understand. I will go and read those discussions as soon as possible.

thanks again.

 

[dmacleo]

If all nameserver IP#s point to the same machine then there's no advantage at all to having multiple nameservers.

Jeff

TBH I did it only because my server had 5 ips and registrar required 2 to be entered to point NS of domains.