Solved

DNS not letting out to website

Posted on 2008-10-05
3
256 Views
Last Modified: 2012-05-05
I have a domain name that is the same name as the website name (name.com), so I have a domain and a website, but the website is hosted off the domain.  When a user tries to get to the website, the DNS server thinks its talking about it and doesnt let through.  I have verifed this by pinging the FQDN of the website and the DNS server replies with its (the local DNS server's) IP address.  How do i create the passtrough so that a user can get to the website name from internally.
0
Comment
Question by:cheifm0j0
3 Comments
 
LVL 4

Accepted Solution

by:
placebo69a earned 500 total points
ID: 22645794
Hi there!
The problem you're describing is not uncommon. This is what happens when you name your domain after an existing Internet website. The way your domain works means it uses DNS to identify the different servers which play roles in it, namely Domain Controllers. If you are running your domain in a Native 2003 Mode (This is only possible if all your Domain Controllers run Windows Server 2003) then you can use the Active Directory Domain Rename Tools to change your domain name, linked here. Once you've changed your domain name you should have no trouble accessing the website.
If you choose not to change your domain name access to the website that has the same name as your domain is possible, but not practical. You can create a static Pointer Record (AKA An A Record) leading to the website but it cannot use your domain name. The result is that any links in the website will probably fail as they will not have the changed name you must use.
Let me know if this helps. :)
0
 
LVL 38

Expert Comment

by:ChiefIT
ID: 22645819
I have never run into the problem myself. But, I think I have seen this work well by creating a static HOST A record in DNS, (((((as placebo69 says)))))). But, add the WWW to the host A account so it will route through forwarders or root hint servers.

xxx.xxx.xxx.xxx   www.servername.domain.name

where xxx.xxx.xxx.xxx is the outside IP of the server.
0
 
LVL 16

Expert Comment

by:robrandon
ID: 22649345
If the domain name has a suffix, such as WWW, you can create an A record that points to the public IP address of the web server.

If it does not contain a suffix, such as http://domainname.com, and domainname is your internal domain, I don't believe you will be able to resolve it properly.  This is due to your server hosting DNS for that domain.
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Numerous times I have been asked this questions that what is it that makes my machine log on so slow, there have been cases where computers took 23 minute exactly after taking password and getting to the desktop. Interesting thing was the fact th…
There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
A company’s greatest vulnerability is their email. CEO fraud, ransomware and spear phishing attacks are the no1 threat to a company’s security. Cybercrime is responsible for the largest loss of money to companies today with losses projected to r…

930 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now