Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > DNS Server > creating name servers

Reply
Thread Tools Display Modes

creating name servers

 
 
shank
Guest
Posts: n/a

 
      06-06-2009
Rookie here... I have an FTP site setup behind a router. Works fine with IP
address. Now I want to use it with a domain name. I wanted to create a name
server and point the FTP domain at that. My steps so far were...

(All fake IP and domains)

1) MyNameServer.com is hosted on GoDaddy
I created A records ns1.MyNameServer.com & ns2.MyNameServer.com
I have one static IP: 60.60.60.60
ns1.MyNameServer.com resolves to: 60.60.60.60
ns2.MyNameServer.com resolves to: 60.60.60.60 (I know - pointless)

2) I have FTPDomain.com and set its name servers to: ns1.MyNameServer.com &
ns2.MyNameServer.com

3) I went into my Windows Server 2003 and setup A record for
ns1.MyNameServer.com pointing at: 192.168.10.5

4) I went into WS2003 and setup A record for www.FTPDomain.com and also
ftp.FTPDomain.com both pointing at: 192.168.10.5

5) I can connect with 60.60.60.60 in an FTP client or ftp://60.60.60.60 with
a browser.
I can neither connect or ping successfully: ftp.FTPDomain.com or
MyNameServer.com.

Am I looking at this right? I'm thinking as long as I create a name server
pointed at a specific IP, and I then use that name server on any domain, the
domain should resolve to my WS2003, correct? Then, setting up a forward
zone, should resolve the domain within the WS2003, correct?

Where am I messing up?
thanks


 
Reply With Quote
 
 
 
 
Ace Fekay [Microsoft Certified Trainer]
Guest
Posts: n/a

 
      06-07-2009
"shank" <> wrote in message
news:...
> Rookie here... I have an FTP site setup behind a router. Works fine with
> IP address. Now I want to use it with a domain name. I wanted to create a
> name server and point the FTP domain at that. My steps so far were...
>
> (All fake IP and domains)
>
> 1) MyNameServer.com is hosted on GoDaddy
> I created A records ns1.MyNameServer.com & ns2.MyNameServer.com
> I have one static IP: 60.60.60.60
> ns1.MyNameServer.com resolves to: 60.60.60.60
> ns2.MyNameServer.com resolves to: 60.60.60.60 (I know - pointless)
>
> 2) I have FTPDomain.com and set its name servers to: ns1.MyNameServer.com
> & ns2.MyNameServer.com
>
> 3) I went into my Windows Server 2003 and setup A record for
> ns1.MyNameServer.com pointing at: 192.168.10.5
>
> 4) I went into WS2003 and setup A record for www.FTPDomain.com and also
> ftp.FTPDomain.com both pointing at: 192.168.10.5
>
> 5) I can connect with 60.60.60.60 in an FTP client or ftp://60.60.60.60
> with a browser.
> I can neither connect or ping successfully: ftp.FTPDomain.com or
> MyNameServer.com.
>
> Am I looking at this right? I'm thinking as long as I create a name server
> pointed at a specific IP, and I then use that name server on any domain,
> the domain should resolve to my WS2003, correct? Then, setting up a
> forward zone, should resolve the domain within the WS2003, correct?
>
> Where am I messing up?
> thanks
>



You can't ping from the inside network or the outside? Also, are you saying
it resolves and doesn't respond to a ping, or it doesn't even resolve??

If you can't ping from external, same question above. Also, did you port
remap FTP (TCP 21 & TCP 20) to 192.168.10.5?

For internal use, as long as your machines are only pointing to the internal
DNS server you've created the records on, then it should resolve.

And yes, ICANN requires two nameservers to be SOA for a domain, with
separate names and IPs.

Also, you shouldn't pick a public IP. Just use X's, such as x.x.x.x or
60.x.x.x. The one you picked actually belongs to someone in Japan. Did you
get their permission to use it?


--
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer


For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right
things." - Peter F. Drucker
http://twitter.com/acefekay



 
Reply With Quote
 
Paul Bergson [MVP-DS]
Guest
Posts: n/a

 
      06-09-2009
ns1.MyNameServer.com resolves to: 60.60.60.60
ns2.MyNameServer.com resolves to: 60.60.60.60 (I know - pointless)

1) Confusing. Are you saying these two name server resolve to 60.60.60.60
or they resolve a client to 60.60.60.60?


2) Fine that you have set the ftp server to resolve from these name servers
but what about the clients that are going to use this dns server in your
tests?
3) What does this mean, not enough info (What is this server)?
4) no clue what you are doing

Lets make it simple (3, 4 and 5 are to confusing for me so remove and follow
below this may be what you siad but I don't follow)
Once GoDaddy has setup the resolution for you simply do an nslookup on a
client machine. If the dns name on the ftp server is the same as the
internal dns name then you will need to add a host record internally (On you
internal dns) to point to the ftp server. If you can't get this to work
obviously pinging won't work nor will anything else.


Also if you plan on exposing your external ip address why are you using a
fake ip address? If nothing else just change the first octet or two, the
number you chose is just one more confusion point.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"shank" <> wrote in message
news:...
> Rookie here... I have an FTP site setup behind a router. Works fine with
> IP address. Now I want to use it with a domain name. I wanted to create a
> name server and point the FTP domain at that. My steps so far were...
>
> (All fake IP and domains)
>
> 1) MyNameServer.com is hosted on GoDaddy
> I created A records ns1.MyNameServer.com & ns2.MyNameServer.com
> I have one static IP: 60.60.60.60
> ns1.MyNameServer.com resolves to: 60.60.60.60
> ns2.MyNameServer.com resolves to: 60.60.60.60 (I know - pointless)
>
> 2) I have FTPDomain.com and set its name servers to: ns1.MyNameServer.com
> & ns2.MyNameServer.com
>
> 3) I went into my Windows Server 2003 and setup A record for
> ns1.MyNameServer.com pointing at: 192.168.10.5
>
> 4) I went into WS2003 and setup A record for www.FTPDomain.com and also
> ftp.FTPDomain.com both pointing at: 192.168.10.5
>
> 5) I can connect with 60.60.60.60 in an FTP client or ftp://60.60.60.60
> with a browser.
> I can neither connect or ping successfully: ftp.FTPDomain.com or
> MyNameServer.com.
>
> Am I looking at this right? I'm thinking as long as I create a name server
> pointed at a specific IP, and I then use that name server on any domain,
> the domain should resolve to my WS2003, correct? Then, setting up a
> forward zone, should resolve the domain within the WS2003, correct?
>
> Where am I messing up?
> thanks
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
RE: No access to other servers from joined Standard 2003 servers Miles Li [MSFT] Windows Small Business Server 0 09-04-2008 11:36 AM
Is there any tool to enumerate all servers in a domain, including hidden servers? Mike Matheny Active Directory 8 09-22-2006 09:14 PM
Swithing from office servers to alternative backup servers - email / domain setup question news.microsoft.com Windows Server 10 08-07-2006 06:39 PM
re: External Trust Between Windows 2000 Native Domains (One with 2K servers, and one with 2K3 servers) rick.kingslan@microsoft.com Active Directory 0 10-26-2005 05:37 PM
Problems automatically creating an e-mail address when creating a Henry Windows Small Business Server 8 04-28-2005 06:47 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59