04-28-2008 08:18 AM - edited 03-03-2019 09:43 PM
Hi,
I am wondering how I can get the machines on my internal network to find my server as currently they are finding http server on my 857W and instead of my website I am getting into SDM!
I can get from WAN to LAN fine as port 80 has been forwarded to my server IP address but I think it's something to do with my dhcp dns relay.
I have included my config file and I would be greatful for any help and assistance!
Thanks in advance
05-05-2008 08:43 PM
I tried putting the FQDN into the web browser of my server through an X11 tunnel over ssh with no luck! The server keeps referring to the WAN address.
My zone file is:
;
; BIND data file for optiplex-networks.db
; /var/named/optiplex-networks.db
;
@ IN SOA optiplex-networks.tk. optiplex-networks.tk. (
2008050601 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Default TTL
IN NS dns.optiplex-networks.tk.
IN MX 10 mail.optiplex-networks.tk.
www IN A 192.168.1.51
news IN A 192.168.1.51
mail IN A 192.168.1.51
dns IN A 192.168.1.51
dns2 IN A 192.168.1.1
So definately the problem either lies with the DNS config in the server or the router itself. The server is also set to master DNS mode.
05-06-2008 06:14 AM
Hi, I've managed to make some progress!
I created a new zone file:
;
; BIND data file for example.com
;
$TTL 604800
@ IN SOA optiplex-networks.tk. info.optiplex-networks.tk. (
2008051603 ; Serial
7200 ; Refresh
120 ; Retry
2419200 ; Expire
604800) ; Default TTL
;
@ IN NS optiplex-networks.tk.
#@ IN NS ns2.example.com.
optiplex-networks.tk. IN MX 10 mail.optiplex-networks.tk.
optiplex-networks.tk. IN A 192.168.1.51
www IN CNAME www.optiplex-networks.tk.
mail IN A 192.168.1.51
ftp IN CNAME ftp.optiplex-networks.tk.
optiplex-networks.tk. IN TXT "v=spf1 ip4:192.168.1.51 a mx ~all"
mail IN TXT "v=spf1 a -all"
Now I can resolve http://optiplex-networks.tk and ftp://optiplex-networks.tk internally from the server (well actually over my X11 tunnel) but still at least it's something!
However from my PC when I try to access the URL I can't get to it and my router keeps sending me through the WAN port again?
05-06-2008 06:51 AM
In the DNS you have to setup your router as forwarder. But at the same time I have no confidence that your router is working properly.
on your linux do :
nslookup [enter]
server 192.168.1.1 [enter]
www.cisco.com [enter]
IF it resloves properly then work on your linux machine and set the forwarder address there. Otherwise you need to verify with DNS settings on the router.
05-06-2008 03:43 PM
This si the output of the nslookup:
kayasaman@Vaio:~$ nslookup
> server 192.168.1.1
Default server: 192.168.1.1
Address: 192.168.1.1#53
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
Name: www.cisco.com
Address: 198.133.219.25
05-06-2008 06:49 PM
Is this correct? If not and there is a problem with the DNS implementation within the router how can I correct it?
Previously before using Cisco, all I had to do was put in the gateway address 192.... and the DNS would resolve. There is a big difference however between Cisco and consumer based routers and I'm still learning about IOS and networking, including server construction as I go along so any advice or howto's are really apprieciated.
Thanks
05-06-2008 07:53 PM
Yes the router forwards DNS properly,
Now you have to configure the forwarder in your DNS using ip address of the router and test it.
Your DNS should be able resolve www.cisco.com to it's public ip.
Once that's done you need to reconfigure the DHCP pool on the router and re-point your clients to your new DNS server.
-serg
05-06-2008 08:30 PM
I've just discovered this site: http://blog.ioshints.info/2006/09/use-your-cisco-router-as-primary-dns.html
which gives an idea of how to use router as a domain forwarder:
ip dns server
ip dns primary website.com soa ns.website.com
admin@website.com 86400 3600 1209600 86400
ip host website.com mx 10 mail.website.com
ip host website.com mx 20 mail.isp.com
I'm just wondering for this to work if I had to change the routers domain name to ns1.website??
05-06-2008 09:15 PM
05-07-2008 08:57 AM
Your router is a forwarder already. Personally, I see no need for additional config other than changing DNS IP address in the dhcp scope once your linux box can correctly resolve internal and external IPs.
-serg
05-07-2008 10:19 AM
I understand! I mean this was a crash course in DNS for me by building it into the server anyway so I will post on the Debian forum to see if anyone can help me with Bind9 over there, then I will revert back to the original config and see what happens.
Thanks a lot anyway for all your help and advice :-)
05-07-2008 11:42 AM
Serg, if you don't mind I would like to know when the config I have currently in the router would be used?
I am just keen to learn that's all!
Also, I know it's probably not the place here to ask but since you are the "Pro" I was just hoping for some advice; I am very keen on computer networking ever since I finished my degree in electronic engineering 2 years ago and would like to start up a company offering various IT services to businesses. I am currently thinking of taking a Cisco certificate course but haven't got a clue which one to go for.
Since you have a lot of experience in the field I was just hoping that maybe you could either offer me some tips or help me get a direction.
Kaya
05-07-2008 01:54 PM
Well, not sure about the question you asking about your router.. The config is pretty standard for VPDN tunnel server. You can do a serach on cisco.com and learn more if you are interested.
As for the courses I would start from basic CCNA course and learn the foundations. That would be my advise. Gat a lab setup, play with gear, have fun ;) good luck.
-serg
05-08-2008 03:45 AM
In terms of the config question about the router I was referring to the DNS forwarding part since you said that I shouldn't have to implement it since the DNS in my server should automatically transfer.
So I was wondering when DNS forwarding like I have done would be used?
As an extra, you said that I have standard config for a vpdn tunnel server but however when I try to access with Cisco VPN client I cannot connect?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide