DNS Internet

  • Thread starter Thread starter Parvardigar
  • Start date Start date
P

Parvardigar

My hope is to be advised to any insightful article -ideally, a
solution. Being the owner of the company, and the WAN, I'll get
complaints when there is a lingering problem. Last week several
users, advertising department, told me they couldn't access the
company web site to view our ads. I'll use http://company.com in our
conversation. I instructed our Sysadmin to fix it. It's several days
and nothing is corrected.

I elected to investigate because the issue is not fixed. I went to
several computers to look at company.com. The page would not load up.
I went to my personal computer. Company.com came up. I could go to the
company site because I'm not on the network. I'm connected to our ISP
-55.49.x.x. bypassing network services and so forth. The network
users are accessing the internet via the server PDC 192.168.x.x. to
access the internet. Everyone in the world can look at company.com.
except our company users.

I informed our Sysadmin my findings. He said oh yes it's DNA and the
Alias. The situation is unresolved. Is there a remedy here? It feels
so uncomplicated. Our advertising department is frustrated not being
able to interface with clients who are able to inspect our products.
I'm willing to correct this DNS situation if I can be instructed. We
run Windows 2000 PDC Domain Controller. 2000 Terminal Server, Citrix.
Thanks for any help.
 
Hello Parvardigar,

So you can open the website from the internet and not from the internal network?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
 
In
Parvardigar said:
My hope is to be advised to any insightful article -ideally, a
solution. Being the owner of the company, and the WAN, I'll get
complaints when there is a lingering problem. Last week several
users, advertising department, told me they couldn't access the
company web site to view our ads. I'll use http://company.com in our
conversation. I instructed our Sysadmin to fix it. It's several days
and nothing is corrected.

I elected to investigate because the issue is not fixed. I went to
several computers to look at company.com. The page would not load up.
I went to my personal computer. Company.com came up. I could go to the
company site because I'm not on the network. I'm connected to our ISP
-55.49.x.x. bypassing network services and so forth. The network
users are accessing the internet via the server PDC 192.168.x.x. to
access the internet. Everyone in the world can look at company.com.
except our company users.

I informed our Sysadmin my findings. He said oh yes it's DNA and the
Alias. The situation is unresolved. Is there a remedy here? It feels
so uncomplicated. Our advertising department is frustrated not being
able to interface with clients who are able to inspect our products.
I'm willing to correct this DNS situation if I can be instructed. We
run Windows 2000 PDC Domain Controller. 2000 Terminal Server, Citrix.
Thanks for any help.
Click to expand...


I'm thinking the same thing as Meinolf, that the internal AD and external
public zone are the same name.

All you would have to do, if this is the case, is manually create a www
record under company.com pointing to the private 192.168.x.x address.
Unfortunately trying to connect to http://company.com is a little more
complex since the names are the same and will conflict with the the netlogon
service registered LdapIpAddress. If you want to make this happen, you can
install IIS on each and every DC, and then under the default website on each
machine, configure a redirect to http://www.company.com.


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations
 
InParvardigar <[email protected]> typed:








I'm thinking the same thing as Meinolf, that the internal AD and external
public zone are the same name.

All you would have to do, if this is the case, is manually create a www
record under company.com pointing to the private 192.168.x.x address.
Unfortunately trying to connect to http://company.com is a little more
complex since the names are the same and will conflict with the the netlogon
service registered LdapIpAddress. If you want to make this happen, you can
install IIS on each and every DC, and then under the default website on each
machine, configure a redirect tohttp://www.company.com.

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations- Hide quoted text -

- Show quoted text -
Click to expand...

I'll want to respond. For several years we were just fine accessing
our web site. No problems. Recently the sysadmin altered something. I
need to figure out how to return to 'normal'. My second comment:

Thanks for looking into this topic. I'll want to study your comments,
again. I came into work to look into this a little deeper. I did a
ping from the client machine our server name ping company.com

Pinging company.com [192.168.254.5] with 32 bytes of data

Reply from 192.168.254.13: bytes=32 time<10ms TTL=128
Reply from 192.168.254.13: bytes=32 time<10ms TTL=128
Reply from 192.168.254.13: bytes=32 time<10ms TTL=128
Reply from 192.168.254.13: bytes=32 time<10ms TTL=128

From my independent machine:

Ping company.com
Reply from 82.90.166.34: bytes=32 time<10ms TTL=128
Reply from 82.90.166.34: bytes=32 time<10ms TTL=128
Reply from 82.90.166.34: bytes=32 time<10ms TTL=128
Reply from 82.90.166.34. bytes=32 time<10ms TTL=128

I'll want to thoroughly study your comments to figure out exactly how
to get from internal domain company.com to our website page
index.company.com armed with the knowledge that both are the same
names. At least I'm getting informed, as I become involved.

Thanks
 
In
Parvardigar said:
I'll want to respond. For several years we were just fine accessing
our web site. No problems. Recently the sysadmin altered something. I
need to figure out how to return to 'normal'. My second comment:

Thanks for looking into this topic. I'll want to study your comments,
again. I came into work to look into this a little deeper. I did a
ping from the client machine our server name ping company.com

Pinging company.com [192.168.254.5] with 32 bytes of data

Reply from 192.168.254.13: bytes=32 time<10ms TTL=128
Reply from 192.168.254.13: bytes=32 time<10ms TTL=128
Reply from 192.168.254.13: bytes=32 time<10ms TTL=128
Reply from 192.168.254.13: bytes=32 time<10ms TTL=128

From my independent machine:

Ping company.com
Reply from 82.90.166.34: bytes=32 time<10ms TTL=128
Reply from 82.90.166.34: bytes=32 time<10ms TTL=128
Reply from 82.90.166.34: bytes=32 time<10ms TTL=128
Reply from 82.90.166.34. bytes=32 time<10ms TTL=128

I'll want to thoroughly study your comments to figure out exactly how
to get from internal domain company.com to our website page
index.company.com armed with the knowledge that both are the same
names. At least I'm getting informed, as I become involved.

Thanks
Click to expand...

You are welcome. The differences in the responses to your pings would be
dependendent on what DNS servers it is querying. In an AD infrastructure,
you MUST only use the internal DNS. Apparently the independent machine, as
you mentioned in a previous post, is using the ISP's. Of course this is not
a good solution for AD members because it will cause numerous problems.

When you ping company.com, it will respond with one of the LdapIpAddresses
in DNS. They are the addresses of all your DCs in the form of (and each DC
will register this record because the AD's netlogon service registers it. It
is an important record that you do NOT want to mess with:

(same as parent) A 192.168.254.13
(same as parent) A 192.168.254.x
etc

Is 82.90.166.34 the actual address of your website? Are you hosting it
internally or somewhere else on the Internet??

I am not sure what the admin did to 'fix' or change something, but if
192.168.254.13 is a DC, then it is working properly. What happens when you
ping www.company.com from an internal machine?

If you are hosting the website internall, then manually create the www
record with the internal webserver's private IP.

If it is being hosted externally, manually create the www record with the
external IP of 82.90.166.34, assuming that is the IP.

In any case, assuming the internal domain name and the external public
domain name is the same, the internal users, to make it easier, must NOT use
http://company.com. They should use www.company.com only, unless you want to
go thru the additional steps I previously mentioned.

Ace
 
In Ace Fekay [MVP] <[email protected]> typed:


Also, one more thing, if the website is hosted externally, the ISP may
change the IP address of the website. If the ISP uses a web server farm,
meaning multiple IPs point back to the website, then I can see this being a
problem. To handle that, instead of creating www wtih the external IP, I
would suggest to create a delegation:

rt-click company.com, choose delegation, type in www, and provide the
external publicly held DNS servers' addresses. This way it will always
query those servers for the current IP.

This post is of course assuming it is being held externally.

If internal, my other post explains how to take care of it.

Ace
 
InAce Fekay [MVP] <[email protected]> typed:

Also, one more thing, if the website is hosted externally, the ISP may
change the IP address of the website. If the ISP uses a web server farm,
meaning multiple IPs point back to the website, then I can see this being a
problem. To handle that, instead of creating www wtih the external IP, I
would suggest to create a delegation:

rt-click company.com, choose delegation, type in www, and provide the
external publicly held DNS servers' addresses. This way it will always
query those servers for the current IP.

This post is of course assuming it is being held externally.

If internal, my other post explains how to take care of it.

Ace
Click to expand...

I'm very grateful for your attentions. This DNS is becoming clearer.
Our website www.company.com is external. Company.com is internal.
Internal we have 192.168.254.13 company.com
External we have 82.90.166.34 www.company.com
When I pinged www.company.com prior to implementing your instructions
I received 'unknown host www.company.com'

Then 'rt-click company.com, choose delegation, type in www, and
provide the external publicly held DNS servers' addresses.' -I
followed these instructions. Now I'm able to receive 192.168.254.13
www.laeyeworks.com. It's working -almost. I'm not getting out to the
internet. I'm directed to the company-pdc 192.168.254.13

At least I am progressing. From DNS Server I rt click Company.com >
New Delegation .
The FQDN indicates 'Company.com'. I could only type in 'www' in order
to apply 'next'. The next screen my options were 'add and ip'. Into
'Add' I typed in www.company.com. I typed into IP '82.90.166.34' . I
was allowed to proceed to finish.

After this procedure I could ping www.company.com. The host was found.
That was good news. But it's picking up the company.com pdc
192.168.254.13. Even though the delegations instructions are "NS
www.company.com IP 82.90.166.34" -DNS is kicking the instructions into
www.company.com 192.168.254.13

The smell of success feels so close. Please let me know how to force
DNS to accept 82.90.166.34 www.company.com -and this should fix the
company's users ability to access, via the internet, www.company.com

Thanks
 
In
Parvardigar said:
On Dec 30, 10:20 pm, "Ace Fekay [MVP]" <[email protected]>
wrote:

I'm very grateful for your attentions. This DNS is becoming clearer.
Our website www.company.com is external. Company.com is internal.
Internal we have 192.168.254.13 company.com
External we have 82.90.166.34 www.company.com
When I pinged www.company.com prior to implementing your instructions
I received 'unknown host www.company.com'

Then 'rt-click company.com, choose delegation, type in www, and
provide the external publicly held DNS servers' addresses.' -I
followed these instructions. Now I'm able to receive 192.168.254.13
www.laeyeworks.com. It's working -almost. I'm not getting out to the
internet. I'm directed to the company-pdc 192.168.254.13

At least I am progressing. From DNS Server I rt click Company.com >
New Delegation .
The FQDN indicates 'Company.com'. I could only type in 'www' in order
to apply 'next'. The next screen my options were 'add and ip'. Into
'Add' I typed in www.company.com. I typed into IP '82.90.166.34' . I
was allowed to proceed to finish.

After this procedure I could ping www.company.com. The host was found.
That was good news. But it's picking up the company.com pdc
192.168.254.13. Even though the delegations instructions are "NS
www.company.com IP 82.90.166.34" -DNS is kicking the instructions into
www.company.com 192.168.254.13

The smell of success feels so close. Please let me know how to force
DNS to accept 82.90.166.34 www.company.com -and this should fix the
company's users ability to access, via the internet, www.company.com

Thanks
Click to expand...

If you did the following:
Then 'rt-click company.com, choose delegation, type in www, and
provide the external publicly held DNS servers' addresses.' -I
followed these instructions. Now I'm able to receive 192.168.254.13
www.laeyeworks.com. It's working -almost. I'm not getting out to the
internet. I'm directed to the company-pdc 192.168.254.13
Click to expand...

Then it will not work. I specifically said when creating the www delegation,
to supply the external DNS servers that are SOA of the public zone. These
are the two DNS servers hosting your external zone.
Non-authoritative answer:
laeyeworks.com nameserver = ns416.hostgator.com
laeyeworks.com nameserver = ns415.hostgator.com
Try that with the delegation and let me know.

Ace
 
InParvardigar <[email protected]> typed:












If you did the following:


Then it will not work. I specifically said when creating the www delegation,
to supply the external DNS servers that are SOA of the public zone. These
are the two DNS servers hosting your external zone.
Non-authoritative answer:
laeyeworks.com nameserver = ns416.hostgator.com
laeyeworks.com nameserver = ns415.hostgator.com



Try that with the delegation and let me know.
Click to expand...
I understand your comment on SOA external DNS server. I did an edit on
www delegation changing to ns415.hostgator.com ns416.hostgator.com
with the appropriate ip address. I can ping the ip address,
successfully. I can ping ns416.hostgator.com, successfully. I can do
this on the internal computers, successfully, and the external
computer, successfully. I am unable to open our web page using the IE
browser, internally.

I went into the server room to inspect the PDC. Using the browser I
was invited to log in to the web site? This event was unexpected. Once
logged in as Admin the cryptic message stated: "You do not currently
have a default document set for your users. Any users attempting to
connect to this site are currently receiving an 'under construction
page'. And that is exactly what is happening internally. This login
feature, and the message delivered, is -unexpected. This anomaly
should have been corrected long ago. These last several weeks our ad
department agonized wanting to have unfettered access to the web site.
Is there a solution with this current development? This scenario is
totally unexpected. I can't figure out what is unfolding behind the
scenes. At least the delegation fits and I am most appreciative. Again
thanks for your attentions.
 
In
Parvardigar said:
I understand your comment on SOA external DNS server. I did an edit on
www delegation changing to ns415.hostgator.com ns416.hostgator.com
with the appropriate ip address. I can ping the ip address,
successfully. I can ping ns416.hostgator.com, successfully. I can do
this on the internal computers, successfully, and the external
computer, successfully. I am unable to open our web page using the IE
browser, internally.

I went into the server room to inspect the PDC. Using the browser I
was invited to log in to the web site? This event was unexpected. Once
logged in as Admin the cryptic message stated: "You do not currently
have a default document set for your users. Any users attempting to
connect to this site are currently receiving an 'under construction
page'. And that is exactly what is happening internally. This login
feature, and the message delivered, is -unexpected. This anomaly
should have been corrected long ago. These last several weeks our ad
department agonized wanting to have unfettered access to the web site.
Is there a solution with this current development? This scenario is
totally unexpected. I can't figure out what is unfolding behind the
scenes. At least the delegation fits and I am most appreciative. Again
thanks for your attentions.
Click to expand...

Ok, maybe I am misunderstanding your setup. Maybe it's me? I am getting
somewhat confused with your responses and your configuration as you are
describing it. I think it maybe coming down to terminology and not being
specific on your part? I am not sure, therefore I am asking you to be very
specific in future responses.

1. Are you sayin your website is hosted externally AND internally?? Or is it
just externally?

2. When you went to the server room to "inspect" your DC (notice - there is
no such thing as a PDC with Windows 2000 and newer, that is an old NT4
term), what was the exact URL you type in the browser?

Note:
If you typed in http://laeyeworks.com and you got your local machine's
website or one of the DC's IIs, then that is TOTALLY expected. If you did
not get that, then I would imagine something is wrong with AD.

Ace
 
InParvardigar <[email protected]> typed:







Ok, maybe I am misunderstanding your setup. Maybe it's me? I am getting
somewhat confused with your responses and your configuration as you are
describing it. I think it maybe coming down to terminology and not being
specific on your part? I am not sure, therefore I am asking you to be very
specific in future responses.

1. Are you sayin your website is hosted externally AND internally?? Or is it
just externally?

2. When you went to the server room to "inspect" your DC (notice - there is
no such thing as a PDC with Windows 2000 and newer, that is an old NT4
term), what was the exact URL you type in the browser?

Note:
If you typed inhttp://laeyeworks.comand you got your local machine's
website or one of the DC's IIs, then that is TOTALLY expected. If you did
not get that, then I would imagine something is wrong with AD.

Ace- Hide quoted text -

- Show quoted text -
Click to expand...

Yes. It may be terminology. Sorry. I'm from the NT days. The website
is hosted externally. Within the company we would want to simply type
in www.laeyeworks.com - Which is what I did at the client machine(s).
I elected to log into the Server (DC). I opened up IE. I typed into
the address bar www.laeyeworks.com. I did not type in http://laeyeworks.com
That's when (all this is new to me) the login interface appeared
prompting me to log into laeyeworks.com. Username; Password; Domain.
That's when the cryptic message appeared. And to my surprise IIs type
information was presented.

We never did use IIS. Internally the company is a database/ financial
enterprise. It looks as though the sysadmin may be experimenting. I
don't know.

The web site is hosted externally. If the ad department wants to alter
content the web creator is instructed. When the website is updated
(externally) our ad department is notified. That's when they go onto
the webpage to view the update. However, recently, the last several
weeks, we have lost that ability to view our website.

I hope this comment helps. And I apologize for my amateurish non
technical syntax.
 
In
Parvardigar said:
Yes. It may be terminology. Sorry. I'm from the NT days. The website
is hosted externally. Within the company we would want to simply type
in www.laeyeworks.com - Which is what I did at the client machine(s).
I elected to log into the Server (DC). I opened up IE. I typed into
the address bar www.laeyeworks.com. I did not type in
http://laeyeworks.com That's when (all this is new to me) the login
interface appeared
prompting me to log into laeyeworks.com. Username; Password; Domain.
That's when the cryptic message appeared. And to my surprise IIs type
information was presented.

We never did use IIS. Internally the company is a database/ financial
enterprise. It looks as though the sysadmin may be experimenting. I
don't know.

The web site is hosted externally. If the ad department wants to alter
content the web creator is instructed. When the website is updated
(externally) our ad department is notified. That's when they go onto
the webpage to view the update. However, recently, the last several
weeks, we have lost that ability to view our website.

I hope this comment helps. And I apologize for my amateurish non
technical syntax.
Click to expand...

Ok, external. Good. Thank you.

I would like you to delete whatever delegation is created. If a www record
exists, delete that to.

Now create a new delegation for www under the zone laeyeworks.com and
provide the two DNS servers I previously posted:
ns416.hostgator.com [70.87.170.35]
ns415.hostgator.com [70.87.170.35]

Once that is done:
1. In DNS, rt-click the DNS server name and choose Delete Cache (this
deletes the DNS server's cached lookups so it will get a fresh resolution
for you).

2. On the workstation you are testing it on, go into a CMD prompt, type in
ipconfig /flushdns (this clears the local resolver cache).

3. Open a browser, go to Intenet Options, and delete your temp files. This
deletes previously connected data).

4. Connect to www.laeyeworks.com


Ace
 
InParvardigar <[email protected]> typed:




Yes. It may be terminology. Sorry. I'm from the NT days. The website
is hosted externally.  Within the company we would want to simply type
inwww.laeyeworks.com-  Which is what I did at the client machine(s).
I elected to log into the Server (DC).  I opened up IE. I typed into
the address barwww.laeyeworks.com. I did not type in
http://laeyeworks.comThat's when (all this is new to me) the login
interface appeared
prompting me to log into laeyeworks.com. Username; Password; Domain.
That's when the cryptic message appeared. And to my surprise IIs type
information was presented.
Click to expand...
We never did use IIS. Internally the company is a database/ financial
enterprise. It looks as though the sysadmin may be experimenting. I
don't know.
Click to expand...
The web site is hosted externally. If the ad department wants to alter
content the web creator is instructed. When the website is updated
(externally) our ad department is notified. That's when they go onto
the webpage to view the update. However, recently, the last several
weeks, we have lost that ability to view our website.
Click to expand...
I hope this comment helps. And I apologize for my amateurish non
technical syntax.
Click to expand...

Ok, external. Good. Thank you.

I would like you to delete whatever delegation is created. If a www record
exists, delete that to.

Now create a new delegation for www  under the zone laeyeworks.com and
provide the two DNS servers I previously posted:
ns416.hostgator.com [70.87.170.35]
ns415.hostgator.com [70.87.170.35]

Once that is done:
1. In DNS, rt-click the DNS server name and choose Delete Cache (this
deletes the DNS server's cached lookups so it will get a fresh resolution
for you).

2. On the workstation you are testing it on, go into a CMD prompt, type in
ipconfig /flushdns (this clears the local resolver cache).

3. Open a browser, go to Intenet Options, and delete your temp files. This
deletes previously connected data).

4. Connect towww.laeyeworks.com

Ace- Hide quoted text -

- Show quoted text -
Click to expand...

I feel as though I'm dismantling a bomb. And will proceed cautiously.
I created the www delegation -as instructed -and that is the
delegation I deleted. I was confused with 'delete whatever delegation
is created' as I don't think any additional delegations where created
other than the one delegation that we created, and that delegation was
deleted.

I'm now creating a new delegation. I open the Delegation Wizard. The
FQDN is .laeyworks.com. As I type ns416.hotgator.com in 'Delegated
domain' 'next' becomes disabled after suppling the period at the end
of ns416.(hostgator.com). Thus the 'delegated domain' string becomes
disabled at this point in the string ns416.laeyeworks.com.

Over the last couple days we did, via this exchange, create the new
delegation. Now I'm slightly perplexed that in this current instance I
am unable to create this new delegation.
Incrementally proceding.
Thanks
 
In
Parvardigar said:
I feel as though I'm dismantling a bomb. And will proceed cautiously.
I created the www delegation -as instructed -and that is the
delegation I deleted. I was confused with 'delete whatever delegation
is created' as I don't think any additional delegations where created
other than the one delegation that we created, and that delegation was
deleted.
Click to expand...

I meant to delete any delegation I previously suggested to make so we can
start fresh with the www delegation. I should have been more specific to
instruct you in this. I did not want you to delete any other delegations,
that is if you were to have any created previous to our conversatations. I
apologize for assuming otherwise.

I'm now creating a new delegation. I open the Delegation Wizard. The
FQDN is .laeyworks.com. As I type ns416.hotgator.com in 'Delegated
domain' 'next' becomes disabled after suppling the period at the end
of ns416.(hostgator.com). Thus the 'delegated domain' string becomes
disabled at this point in the string ns416.laeyeworks.com.
Click to expand...


Honestly, creating a delegation is not that difficult. I am surprised we are
having difficulties creating it. I just did it on one of my client's
production machine without a problem. I am not sure where you are having a
problem. Also, I am not exactly sure what you mean by:
...Thus the 'delegated domain' string becomes
disabled at this point in the string ns416.laeyeworks.com.
Click to expand...


Follow these steps:

1. ping ns416.hotgator.com
2. ping ns415.hotgator.com
3. Rt-click laeyeworks.com, choose NEW DELEGATION
4. Click NEXT
5. Type in 'www' (without the quotes)
6. Click ADD
7. Type in 'ns416.hostgator.com' (without the quotes and without an ending
period)
8. Click RESOLVE. Once you hit the resolve button, you will see two entries
in the list now:
66.45.252.236
66.45.252.237
9. Click OK
10. Click ADD again
11. Type in 'ns415.hostgator.com' (without the quotes and without an ending
period)
12. Click RESOLVE. Once you hit the resolve button, you will see two entries
in the list now:
66.45.252.236
66.45.252.237
13. Then hit the OK button.
14. Click NEXT
15. Click FINISH
16. Test it by opening up a web browser and type in
http://www.laeyeworks.com
17. Do NOT use http://laeyeworks.com
18. Tell everyone to ONLY use http://www.laeyeworks.com

Over the last couple days we did, via this exchange, create the new
delegation. Now I'm slightly perplexed that in this current instance I
am unable to create this new delegation.
Incrementally proceding.
Thanks
Click to expand...

There's nothing to be preplexed about this. It's one of the more simpler
tasks in DNS.

Good luck sir.

Ace
 
In

I meant to delete any delegation I previously suggested to make so we can
start fresh with the www delegation. I should have been more specific to
instruct you in this. I did not want you to delete any other delegations,
that is if you were to have any created previous to our conversatations. I
apologize for assuming otherwise.




Honestly, creating a delegation is not that difficult. I am surprised we are
having difficulties creating it. I just did it on one of my client's
production machine without a problem. I am not sure where you are having a
problem. Also, I am not exactly sure what you mean by:


Follow these steps:

1. ping ns416.hotgator.com
2. ping ns415.hotgator.com
3. Rt-click laeyeworks.com, choose NEW DELEGATION
4. Click NEXT
5. Type in 'www' (without the quotes)
6. Click ADD
7. Type in 'ns416.hostgator.com' (without the quotes and without an ending
period)
8. Click RESOLVE. Once you hit the resolve button, you will see two entries
in the list now:
          66.45.252.236
          66.45.252.237
9. Click OK
10. Click ADD again
11. Type in 'ns415.hostgator.com' (without the quotes and without an ending
period)
12. Click RESOLVE. Once you hit the resolve button, you will see two entries
in the list now:
          66.45.252.236
          66.45.252.237
13. Then hit the OK button.
14. Click NEXT
15. Click FINISH
16. Test it by opening up a web browser and type inhttp://www.laeyeworks.com
17. Do NOT usehttp://laeyeworks.com
18. Tell everyone to ONLY usehttp://www.laeyeworks.com




There's nothing to be preplexed about this. It's one of the more simpler
tasks in DNS.

Good luck sir.

Ace
Click to expand...

I'm compelled to respond. And I do apologize. Thank you for your
patience, and infinite indulgence. When I type in
'ns416.hostgator.com' and click on resolve the entry that appears is
70.87.170.35. When I type in 'ns415.hostgator.com' and click on
resolve the entry that appears is 70.87.170.35.

Thus when I finish supplying the information 'ns416.hostgator'
'ns415.hostgator' there is only one entry 70.87.170.35 for both
hostgator.com instances.

I do feel the solution may be eminent. Had the entries 66.45.254.236,
66.45.254.237 come up after hitting the resolve button that may have
been the turning point. Unfortunately only the single entry appeared
70.87.170.35

Sincerely
John M
 
In
Parvardigar said:
I'm compelled to respond. And I do apologize. Thank you for your
patience, and infinite indulgence. When I type in
'ns416.hostgator.com' and click on resolve the entry that appears is
70.87.170.35. When I type in 'ns415.hostgator.com' and click on
resolve the entry that appears is 70.87.170.35.

Thus when I finish supplying the information 'ns416.hostgator'
'ns415.hostgator' there is only one entry 70.87.170.35 for both
hostgator.com instances.

I do feel the solution may be eminent. Had the entries 66.45.254.236,
66.45.254.237 come up after hitting the resolve button that may have
been the turning point. Unfortunately only the single entry appeared
70.87.170.35

Sincerely
John M
Click to expand...

When I tested it, I copied/pasted it from YOUR previous post. You must have
misspelled it. I see that you spelled it as hotgator, but apparently it's
supposed to be hostgator - you missed an "S" in one of your previous post. I
happen to copy/paste the wrong one. I should have looked closer. Use the
correct one.

I copied and pasted it from this passage from your post dated 1/2/2008,
10:05AM EST:
I'm now creating a new delegation. I open the Delegation Wizard. The
FQDN is .laeyworks.com. As I type ns416.hotgator.com in 'Delegated
domain' 'next' becomes disabled after suppling the period at the end
of ns416.(hostgator.com). Thus the 'delegated domain' string becomes
disabled at this point in the string ns416.laeyeworks.com.

Ace
 
Read inline please.

In
Ace Fekay said:
When I tested it, I copied/pasted it from YOUR previous post. You
must have misspelled it. I see that you spelled it as hotgator, but
apparently it's supposed to be hostgator - you missed an "S" in one
of your previous post. I happen to copy/paste the wrong one. I should
have looked closer. Use the correct one.

I copied and pasted it from this passage from your post dated
1/2/2008, 10:05AM EST:
I'm now creating a new delegation. I open the Delegation Wizard. The
FQDN is .laeyworks.com. As I type ns416.hotgator.com in 'Delegated
domain' 'next' becomes disabled after suppling the period at the end
of ns416.(hostgator.com). Thus the 'delegated domain' string becomes
disabled at this point in the string ns416.laeyeworks.com.
Click to expand...

Ace, this is one of those domains a delegation for the www record won't work
for resolving the external website, when the external website has the same
name domain name.
The Public DNS server's www.laeyeworks.com record is a CNAME for
laeyeworks.com. The only thing that will work in this case is to delete the
delegation and create an "A" host record with 70.87.170.84 IP address. This
will give them access by http://www.laeyeworks.com If they want access by
http://laeyeworks.com they will have to get IIS on the DCs to redirect.


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
 
In
Kevin D. Goodknecht Sr. said:
Ace, this is one of those domains a delegation for the www record
won't work for resolving the external website, when the external
website has the same name domain name.
The Public DNS server's www.laeyeworks.com record is a CNAME for
laeyeworks.com. The only thing that will work in this case is to
delete the delegation and create an "A" host record with 70.87.170.84
IP address. This will give them access by http://www.laeyeworks.com
If they want access by http://laeyeworks.com they will have to get
IIS on the DCs to redirect.
Click to expand...

Shoooot. I didn't catch that. I re-ran an nslookup on it, and yes it points
back to the Ldap name. Shooot.

Good catch, Kevin.

Well, John M, sorry about that. My sincere and humble apologies. Delete the
delegation and just create the A record.

Ace
 
In

Shoooot. I didn't catch that. I re-ran an nslookup on it, and yes it points
back to the Ldap name. Shooot.

Good catch, Kevin.

Well, John M, sorry about that. My sincere and humble apologies. Delete the
delegation and just create the A record.

Ace
Click to expand...

On January 3 I got stuck. And resisted returning here not wanting to
be too pesky. Today I came in with that long face. And what I read is
very encouraging. If we can get through this snag it will have been a
most amazing voyage.

I created in forward lookup 'new host' with www.laeyeworks.com and IP
70.87.170.84. Now showing in forward lookup is laeyeworks.com and
www.laeyeworks.com. Very good.

In forward lookup www.laeyeworks.com I have type 'A' with data as
70.87.170.84 IP.
So far, so good.

I can ping www.laeyeworks.com successfully. I can ping 70.87.170.84
successfully.

pinging 70.87.170.84 with 32 bytes of data:
Reply from 70.87.170.84: Ping statistics for 70.87.170.84:
Pinging www.laeyeworks.com [70.87.170.84] with 32 bytes of data:
Reply from 70.87.170.84:
Ping statistics for 70.87.170.84:

In the browser I no longer get this 'under construction' or a 'page
not available'. Instead, when entering the address www.laeyeworks.com
I get bounced over into Google.com? I do a seach laeyeworks.com. And
click on that link -voila -directed instantly to google.com At least
this is very encouraging. And once again, thanks for indulging this
fellow, and helping out.

John
 
In

Shoooot. I didn't catch that. I re-ran an nslookup on it, and yes it points
back to the Ldap name. Shooot.

Good catch, Kevin.

Well, John M, sorry about that. My sincere and humble apologies. Delete the
delegation and just create the A record.

Ace
Click to expand...

On January 3 I got stuck. And resisted returning here not wanting to
be too pesky. Today I came in with that long face. And what I read is
very encouraging. If we can get through this snag it will have been a
most amazing voyage.

I created in forward lookup 'new host' with www.laeyeworks.com and IP
70.87.170.84. Now showing in forward lookup is laeyeworks.com and
www.laeyeworks.com. Very good.

In forward lookup www.laeyeworks.com I have type 'A' with data as
70.87.170.84 IP.
So far, so good.

I can ping www.laeyeworks.com successfully. I can ping 70.87.170.84
successfully.

pinging 70.87.170.84 with 32 bytes of data:
Reply from 70.87.170.84: Ping statistics for 70.87.170.84:
Pinging www.laeyeworks.com [70.87.170.84] with 32 bytes of data:
Reply from 70.87.170.84:
Ping statistics for 70.87.170.84:

In the browser I no longer get this 'under construction' or a 'page
not available'. Instead, when entering the address www.laeyeworks.com
I get bounced over into Google.com? I do a seach laeyeworks.com. And
click on that link -voila -directed instantly to google.com At least
this is very encouraging. And once again, thanks for indulging this
fellow, and helping out.

John
 
Back
Top