DNS Server and port 80

[Schoolies]

My ISP (Cox Communications) blocks port 80. Does my DNS Server need port 80 to work?

 

[Entity]

It shouldn't. Port 80 is HTTP.

Why are you running a DNS server?

Rob

 

[Schoolies]

Thank you...

I'm hosting my web site. Ok, great, now i just have to figure out the records that need to be added in dns.

Do you know what I need to put into DNS (A host, cn, mx,srv)? Just to get it to work.

Thanks again.

 

[Schoolies]

Ok, need some help. Could someone tell me what records I need to enter into my DNS server?

Port 80 is blocked by my provider.
I have my website set up on port 69.
We can call my site www.foo.com.
Right now I'm using GoDaddy to forward to my ip address with port 69 specified.
Also, in GoDaddy, I registered two "domain host information"; dns1.foo.com and dns2.foo.com with both of them going to my ip address.

Thanks

 

[Dyehouse1]

For a start DNS uses TCP port 53

As for DNS records try HERE this will give you a rough idea to start with but I think its simply an A record. MX is for mail and PTR are pointers - like a shortcut.

 

[cerial]

Ok, first, a few questions. Do you have your own DNS server on your LAN/WAN? Is this on a Cable modem? What Webserver are you running? Do you run a Firewall?

Let me know and I can try and help you out...

-Cerial

 

[Schoolies]

I have my own DNS server on my LAN.

I'm connected through a cable modem with 2 network cards.

I have no router/no firewall, nothing (mainly because I want to get this workign before I through obsticles in the way).

I'm running IIS from Windows 2000 Server.

Thanks

 

[Schoolies]

anyone have an idea?

 

[dexter333]

According to my Cisco book, DNS uses UDP port 53.

 

[Garion]

Several comments here..

DNS uses TCP port 53 for nslookups and UDP port 53 for zone transfers. I don't think you need to worry about zone transfers. If you want to run a DNS server, you really just need TCP 53 open. I'm sure that your ISP isn't blocking UDP 53, but that's OK, as you probably don't need it.

As I recall from earlier posts, you're running ICS on your server, as well as DNS, DHCP, etc. This means you're using private IP's behind your server for your workstations. Your DNS server knows about these private IP's. If you were to "advertise" your domain to the Internet with your server, you'd be advertising your private IP's, which probably wouldn't work.

The best thing is to find a DNS provider (like godaddy) that will manage your DNS for you, and forward requests to your website. Managing your own DNS is a real pain - There's no reason to do it, if you don't absolutely need to. Your connection to the Internet probably isn't very robust, and you could possibly create more traffic than you might expect.

On DNS names.. An "A" record is a mapping of a hostname to an IP address. "www.foo.com = 24.11.34.243". A CNAME is a way to create an alias. "www.bar.com = www.foo.com, no go look up www.foo.com to find the real IP address" An MX record is like an "A" record, but is only used for routing e-mail. "mail sent to user@foo.com should go to 24.11.34.243 or 24.11.34.241". A SRV record is a way to manage server resources on specific ports, not something that you'd ever use. Not something that I'd ever use, for that matter. That's what BGP, 3DNS and load balancers are for.


- G

 

[Schoolies]

Thanks for the info.

My ISP doesn't block port 53 so I'm still going to try to get the DNS to work ( I want to learn how to do this for future reference).

As I recall from earlier posts, you're running ICS on your server, as well as DNS, DHCP, etc. This means you're using private IP's behind your server for your workstations. Your DNS server knows about these private IP's. If you were to "advertise" your domain to the Internet with your server, you'd be advertising your private IP's, which probably wouldn't work.

How would I get around this problem? Run another DNS server just for the web site? I thought the purpose of NAT was to prevent my private IPs from being published?

I've used GoDaddy and had my web site being forwarded to my IP address and port (69) but directories would not work... ie. if i typed in http://www.foo.com/test , it would give me an error, but if i would type in http://<ip address>:<port>/test , the index page would show up. This was another reason why I wanted to figure out how to run my own dns server.

 

[Dyehouse1]

I dont think you are going to get it working how you would like.

If you did setup the DNS correctly for your internal network then the clients would resolve and go to the appropraite IIS directory. However as you are not using zone transfers and have not registered the domain name with your ISP (to supply DNS) then everyone outisde on the internet would not resolve anyway.

DNS is hierarchical - the top servers replicate down and yours is on the end of the pyramid and not replicating back up so noone out there will use your DNS server to map your domain name.

I hope that makes some sense its not the easiest subject to put into laymans terms!

 

[Schoolies]

Sorry for being stubborn/incompetant but I'm not understanding why this will now work.

I have registered my domain name with GoDaddy.
GoDaddy has the option of registering "Domain Host Information" and this is the description of it from GoDaddy:

Please DO NOT enter "www" as your host name. This is not a redirection service; it will not direct your domain to an IP address. Name servers are used for web hosting purposes. If you are unsure about what a name server is or you need help in registering your name server, please use the "FAQ" or "24x7 Customer Support" links on this page.

So in this Domain Host Information section I put in dns1 and dns2 with my IP address, the same IP address that has the dns server on it.

In the Name Server section I used the dns1 and dns2.foo.com for my name servers.

Questions:

Since I have my name servers linked to my IP address shouldn't I be getting the requests when people type in my domain name?

Why do I need to register my domain name with my ISP "to supply DNS" if I will be running my own DNS server, which should allow to add the necessary resource records to get my site running?

Also, if I'm not going to be able to do this the way I want, why does 2000 Server provide IIS and DNS if you can't host an external website? It can't be designed only for intranets.


Sorry for the mess, all I'm trying to figure out is why I will not be able to host my own dns server/web site if I have my own external IP address. I understand that my ISP has given me this IP address but (Caution: laymans thought coming ) it it shouldn't matter who gives me the IP address as long as I have an external one.

 

[Schoolies]

Anyone out there?

 

[Woodie]

The issue w/ DNS is not that you're running it, but how do OTHER people find out where your domain is.

1. Since I have my name servers linked to my IP address shouldn't I be getting the requests when people type in my domain name?
Only if your DOMAIN RECORD lists your IP address as the AuthoritativeNameServer for SCHOOLIES.com.

2. Why do I need to register my domain name with my ISP "to supply DNS" if I will be running my own DNS server, which should allow to add the necessary resource records to get my site running? See above. It's so OTHER people can find your domain.

3. Also, if I'm not going to be able to do this the way I want, why does 2000 Server provide IIS and DNS if you can't host an external website? It can't be designed only for intranets.
It could be, it's an M$ product. At any rate, the issue is that you want to provide NameResolutionServices (DNS) for the Internet World, but MS doesn't seem to allow for a split DNS, where some records are only available to internal clients, and others are available to ALL clients. The usual solution to this is to use two domains: A public one (SCHOOLIES.com) which only exists on the Internet, and a private one (SCHOOLIES.LOCAL) which only exists on your private network. So, two distinct name-spaces, two unique DNS servers, and no issues.

 

[Schoolies]

Thank you Woodie.

So there is a solution to this whole mess that will satisfy me.... if I get rid of my internal network completely, only have one computer for the public domain of schoolies.com than I should be able to run my DNS Server and IIS and allow other people to view my web site.