PB with bind, DHCP, and mail client Evolution
Glenn.Satchell at uniq.com.au
Wed Jan 23 11:37:08 UTC 2008
>Date: Wed, 23 Jan 2008 00:32:54 +0100
>From: "stephane lepain" <penguindeb at gmail.com>
>To: dhcp-users at isc.org
>Subject: PB with bind, DHCP, and mail client Evolution
>I am a bit confused as far as this is going. I have installed a dhcp server
>and bind for one of my customer. Everything went fine until he couldnt
>connect to his mailbox from his ISP. Strangely enough, he is got two email
>accounts, one with his isp that is giving him DSL connection (that is the
>one he cannot connect to anymore) and another email account a mac.com one
>that he is able to receive email from.
>As far as the comfiguration is going, there is absolutly nothing fency but
>there is the part where I need to double check with you guys.
>First of all
>ddns-update-style none; // I thought I'd better not conflict with the isp's
>authoritative; // I hope that is not conflicting with the isp's.
>option domain-name-servers 192.168.1.7 // his new internal dns server
>option domain-name macitos; // his new domain.
>I dont see anything wrong here with my config. May be I have omitted
>What is worst is that if I ping his pop account from his internal network it
>is going through.
>Any help is much appreciated here as I am completly stuck.
>Cheers to all of you
You need to do some basic troubleshooting here. It is not obvious
whether this is a DHCP problem or not. So you need to go through this
step by step:
1. On the shiby new dns server can you resolve the ISPs pop system
using the local dns server:
If that doesn't work then you need to look at the dns comfiguration and
make sure it is set up to forward non-local dns requests to the ISPs
If it does work, then onto step 2
2. Check the settings on the client, is it getting an IP address ok?
What about the dns server setting? If windows, then you can use
"ipconfig /all" to see settings for IP address, DNS server, domain,
etc. If it's Unix or Linux then check /etc/resolv.conf for settings
that specify the nameserver with the right IP address.
3. Check for any other restrictions by using telnet to connect to the
telnet pop.isp.com 110
You should get some response, such as a prompt or 'pop server ready'
message from the pop server if you can get through.
If that doesn't work there may be firewall restrictions on the ADSL
router or the PC. New versions of windows may not allow an outbound pop
connection for example.
Hope that helps.
More information about the dhcp-users