Networking Woes

Kernels & Hardware, configuring network, installing services

Networking Woes

Postby figroll » 2013-09-13 12:22

Hi guys, first post here, been scouring the FAQ's and general bits and got pretty much used to debian now, I've tried Ubuntu, Fedora and Cent OS and find debian the best (I know Ubuntu is debian based but a load more differences).

So i'm at home with the system, been using this for around 6 months now I can, configure apache, ssh, webmin, samba, proftpd, phpmyadmin, mysql and run terminal via putty. One thing I'm slightly confused about is describing bind9. What I aim to do is run the server on the network currently, hit that in the address bar here's apache and a few projects i'm working on, all good, but further to that I am currently assigning ip's in my hosts file so site1.lan etc. As you know things change, I am very organised and even have a second root mimicking exactly how my online webserver is to simply transfer the files over, update the database move on.

So far so good, but ideally instead of as you know constantly updating the hosts file I am aware of bind, further more I want control over the a records and more importantly mx which I have attempted. bind setup, test.lan assigned to ip, cmd in windows ping test.lan nothing, dig test.lan throws up:

Code: Select all
root@dns:~# dig test.lan

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> test.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56988
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;test.lan.                      IN      A

.                       1800    IN      SOA 2013091300 1800 900 604800 86400

;; Query time: 78 msec
;; WHEN: Fri Sep 13 12:02:26 2013
;; MSG SIZE  rcvd: 101

To be fair as new to bind9 unsure what that is actually saying at a guess nothing has worked however. So further to this, this is how I want to play it really and if you don't mind me asking some questions:

1. I do not want to make this available outside the lan so no need for google, opendns servers.
2. Where does the server reside? I'm connected into the router a not so good sagem sky default, dns ip range going upto .100
3. How do I build the bridge for the network to connect?

I am very willing to learn this, let's call it the last piece of the puzzle to the perfect home office web testing lan!

Thanks in advance :D
I hate being Bi-Polar, It's Awesome!
User avatar
Posts: 7
Joined: 2013-09-13 12:09
Location: Sunderland

Re: Networking Woes

Postby dasein » 2013-09-13 15:08

I confess I still don't know what your question is.

That said, some random thoughts that may or may not prove helpful...

BIND for a local DNS server is like a piano for a paperweight. Effective enough, but massive overkill. If all you are looking to do is run a local DNS server, DNSMasq does the job very nicely, and is vastly easier to configure. There is a bit of a learning curve, but the docs are exemplary.

Your local DNS server is a local machine. Where else would it be?

Based on the error your posted, it looks as if your local machine(s) are unaware of your local DNS server. So I'm guessing that at least part of your issue is incorrectly configured DHCP, and has nothing to do with DNS/BIND/whatever.
User avatar
Posts: 7775
Joined: 2011-03-04 01:06
Location: Terra Incantationum

Re: Networking Woes

Postby figroll » 2013-09-13 15:25

Thanks for the reply, confusing post yes I agree!

Well I've made a development, the dns is on server, I've now pointed my configuration in windows to use this as the preferred server, created a virtual host in apache and it is loading, ping in cmd is receiving packets.

DNSmasq was running on my router into another router but I wanted to pull this out of the equation, does DNSmasq support MX records? I need to test out email server configurations and internal imap mail from the sites contact forms etc, hence, my choice of bind, plus, getting into bind would bypass hiding behind the fact of its complex layout and setup so I thought go for the worst case scenario?

Again thanks for the response
I hate being Bi-Polar, It's Awesome!
User avatar
Posts: 7
Joined: 2013-09-13 12:09
Location: Sunderland

Re: Networking Woes

Postby dasein » 2013-09-13 16:17

figroll wrote:...does DNSmasq support MX records?

Sure, I'll do your searching for you.

Here you go. ... 3F&cat=web
User avatar
Posts: 7775
Joined: 2011-03-04 01:06
Location: Terra Incantationum

Re: Networking Woes

Postby figroll » 2013-09-14 08:36

Well that is interesting, sorry for the inconvinience I should have gave it a search myself, it's one of those things where you write it and think what did I just write there?

You've been more than helpful, see what I come up with now :D

Thanks again and apologies for being lazy there.

*EDIT: Kudo's on startpage too!
I hate being Bi-Polar, It's Awesome!
User avatar
Posts: 7
Joined: 2013-09-13 12:09
Location: Sunderland

Re: Networking Woes

Postby figroll » 2013-09-15 08:52

It seems DNSmasq is not as effective, I again point the network to the DNS server but it would not ping however nslookup did ping back results but on the local ip. So changes made and it still did not work for some reason. Bind however is, I'm surprised at my findings so far, Overhaul absolutely however if I stick with plan A to get to grips with the more complicated software is that a bad thing.
I hate being Bi-Polar, It's Awesome!
User avatar
Posts: 7
Joined: 2013-09-13 12:09
Location: Sunderland

Re: Networking Woes

Postby figroll » 2013-09-17 11:57

So back again, Bind sort of works however in dig there is no answer. This is my setup and perhaps I'm doing something wrong with the "bridge" (connecting the network together).

Desktop Pc >>> wireless router ( - static
Raspberry Pi >>> wireless router ( - static

Desktop Pc (Windows 7) > using preferred dns server > Debian 7 running on raspberry with webserver.

Ping cannot find "test.lan" on the following config:

Code: Select all
# Configuration file for dnsmasq.
# Format is one option per line, legal options are the same
# as the long options legal on the command line. See
# "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details.

# Listen on this specific port instead of the standard DNS port
# (53). Setting this to zero completely disables DNS function,
# leaving only DHCP and/or TFTP.

# The following two options make you a better netizen, since they
# tell dnsmasq to filter out queries which the public DNS cannot
# answer, and which load the servers (especially the root servers)
# unnecessarily. If you have a dial-on-demand link they also stop
# these requests from bringing up the link unnecessarily.

# Never forward plain names (without a dot or domain part)
# Never forward addresses in the non-routed address spaces.

# Uncomment this to filter useless windows-originated DNS requests
# which can trigger dial-on-demand links needlessly.
# Note that (amongst other things) this blocks all SRV requests,
# so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk.
# This option only affects forwarding, SRV records originating for
# dnsmasq (via srv-host= lines) are not suppressed by it.

# Change this line if you want dns to get its upstream servers from
# somewhere other that /etc/resolv.conf

# By  default,  dnsmasq  will  send queries to any of the upstream
# servers it knows about and tries to favour servers to are  known
# to  be  up.  Uncommenting this forces dnsmasq to try each query
# with  each  server  strictly  in  the  order  they   appear   in
# /etc/resolv.conf

# If you don't want dnsmasq to read /etc/resolv.conf or any other
# file, getting its servers from this file instead (see below), then
# uncomment this.

# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv
# files for changes and re-read them then uncomment this.

# Add other name servers here, with domain specs if they are for
# non-public domains.

# these are google's domain name server. OpenDNS is an alternative
# and there are others if you don't want to use google.

# Example of routing PTR queries to nameservers: this will send all
# address->name queries for 192.168.3/24 to nameserver

# Add local-only domains here, queries in these domains are answered
# from /etc/hosts or DHCP only.

# Add domains which you want to force to an IP address here.
# The example below send any host in to a local
# web-server.

# --address (and --server) work with IPv6 addresses too.

# You can control how dnsmasq talks to a server: this forces
# queries to to be routed via eth1
# server=

# and this sets the source (ie local) address used to talk to
# to port 55 (there must be a interface with that
# IP on the machine, obviously).
# server=

# If you want dnsmasq to change uid and gid to something other
# than the default, edit the following lines.

# If you want dnsmasq to listen for DHCP and DNS requests only on
# specified interfaces (and the loopback) give the name of the
# interface (eg eth0) here.
# Repeat the line for more than one interface.
# Or you can specify which interface _not_ to listen on
# Or which to listen on by address (remember to include if
# you use this.)


# If you want dnsmasq to provide only DNS service on an interface,
# configure it as shown above, and then use the following line to
# disable DHCP and TFTP on it.

# On systems which support it, dnsmasq binds the wildcard address,
# even when it is listening on only some interfaces. It then discards
# requests that it shouldn't reply to. This has the advantage of
# working even when interfaces come and go and change address. If you
# want dnsmasq to really bind only the interfaces it is listening on,
# uncomment this option. About the only time you may need this is when
# running another nameserver on the same machine.

# If you don't want dnsmasq to read /etc/hosts, uncomment the
# following line.
# or if you want it to read another file, as well as /etc/hosts, use
# this.

# Set this (and domain: see below) if you want to have a domain
# automatically added to simple names in a hosts-file.


# Set the domain for dnsmasq. this is optional, but if it is set, it
# does the following things.
# 1) Allows DHCP hosts to have fully qualified domain names, as long
#     as the domain part matches this setting.
# 2) Sets the "domain" DHCP option thereby potentially setting the
#    domain of all systems configured by DHCP
# 3) Provides the domain part for "expand-hosts"

# Set a different domain for a particular subnet,


# Same idea, but range rather then subnet,,

# Uncomment this to enable the integrated DHCP server, you need
# to supply the range of addresses available for lease and optionally
# a lease time. If you have more than one network, you will need to
# repeat this for each network on which you want to supply DHCP
# service.


# This is an example of a DHCP range where the netmask is given. This
# is needed for networks we reach the dnsmasq DHCP server via a relay
# agent. If you don't know what a DHCP relay agent is, you probably
# don't need to worry about this.

# This is an example of a DHCP range which sets a tag, so that
# some DHCP options may be set only for this network.

# Use this DHCP range only when the tag "green" is set.

# Specify a subnet which can't be used for dynamic address allocation,
# is available for hosts with matching --dhcp-host lines. Note that
# dhcp-host declarations will be ignored unless there is a dhcp-range
# of some type for the subnet in question.
# In this case the netmask is implied (it comes from the network
# configuration on the machine running dnsmasq) it is possible to give
# an explicit netmask instead.

# Enable DHCPv6. Note that the prefix-length does not need to be specified
# and defaults to 64 if missing/
#dhcp-range=1234::2, 1234::500, 64, 12h

# Do Router Advertisements, BUT NOT DHCP for this subnet.
#dhcp-range=1234::, ra-only

# Do Router Advertisements, BUT NOT DHCP for this subnet, also try and
# add names to the DNS for the IPv6 address of SLAAC-configured dual-stack
# hosts. Use the DHCPv4 lease to derive the name, network segment and
# MAC address and assume that the host will also have an
# IPv6 address calculated using the SLAAC alogrithm.
#dhcp-range=1234::, ra-names

# Do Router Advertisements, BUT NOT DHCP for this subnet.
# Set the lifetime to 46 hours. (Note: minimum lifetime is 2 hours.)
#dhcp-range=1234::, ra-only, 48h

# Do DHCP and Router Advertisements for this subnet. Set the A bit in the RA
# so that clients can use SLAAC addresses as well as DHCP ones.
#dhcp-range=1234::2, 1234::500, slaac

# Do Router Advertisements and stateless DHCP for this subnet. Clients will
# not get addresses from DHCP, but they will get other configuration information.
# They will use SLAAC for addresses.
#dhcp-range=1234::, ra-stateless

# Do stateless DHCP, SLAAC, and generate DNS names for SLAAC addresses
# from DHCPv4 leases.
#dhcp-range=1234::, ra-stateless, ra-names

# Do router advertisements for all subnets where we're doing DHCPv6
# Unless overriden by ra-stateless, ra-names, et al, the router
# advertisements will have the M and O bits set, so that the clients
# get addresses and configuration from DHCPv6, and the A bit reset, so the
# clients don't use SLAAC addresses.

# Supply parameters for specified hosts using DHCP. There are lots
# of valid alternatives, so we will give examples of each. Note that
# IP addresses DO NOT have to be in the range given above, they just
# need to be on the same network. The order of the parameters in these
# do not matter, it's permissible to give name, address and MAC in any
# order.

# Always allocate the host with Ethernet address 11:22:33:44:55:66
# The IP address

# Always set the name of the host with hardware address
# 11:22:33:44:55:66 to be "fred"

# Always give the host with Ethernet address 11:22:33:44:55:66
# the name fred and IP address and lease time 45 minutes

# Give a host with Ethernet address 11:22:33:44:55:66 or
# 12:34:56:78:90:12 the IP address Dnsmasq will assume
# that these two Ethernet interfaces will never be in use at the same
# time, and give the IP address to the second, even if it is already
# in use by the first. Useful for laptops with wired and wireless
# addresses.

# Give the machine which says its name is "bert" IP address
# and an infinite lease

# Always give the host with client identifier 01:02:02:04
# the IP address

# Always give the host with client identifier "marjorie"
# the IP address

# Enable the address given for "judge" in /etc/hosts
# to be given to a machine presenting the name "judge" when
# it asks for a DHCP lease.

# Never offer DHCP service to a machine whose Ethernet
# address is 11:22:33:44:55:66

# Ignore any client-id presented by the machine with Ethernet
# address 11:22:33:44:55:66. This is useful to prevent a machine
# being treated differently when running under different OS's or
# between PXE boot and OS boot.

# Send extra options which are tagged as "red" to
# the machine with Ethernet address 11:22:33:44:55:66

# Send extra options which are tagged as "red" to
# any machine with Ethernet address starting 11:22:33:

# Give a fixed IPv6 address and name to client with
# DUID 00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2
# Note the MAC addresses CANNOT be used to identify DHCPv6 clients.
# Note also the they [] around the IPv6 address are obilgatory.
#dhcp-host=id:00:01:00:01:16:d2:83:fc:92:d4:19:e2:d8:b2, fred, [1234::5]

# Ignore any clients which are not specified in dhcp-host lines
# or /etc/ethers. Equivalent to ISC "deny unknown-clients".
# This relies on the special "known" tag which is set when
# a host is matched.

# Send extra options which are tagged as "red" to any machine whose
# DHCP vendorclass string includes the substring "Linux"

# Send extra options which are tagged as "red" to any machine one
# of whose DHCP userclass strings includes the substring "accounts"

# Send extra options which are tagged as "red" to any machine whose
# MAC address matches the pattern.

# If this line is uncommented, dnsmasq will read /etc/ethers and act
# on the ethernet-address/IP pairs found there just as if they had
# been given as --dhcp-host options. Useful if you keep
# MAC-address/host mappings there for other purposes.

# Send options to hosts which ask for a DHCP lease.
# See RFC 2132 for details of available options.
# Common options can be given to dnsmasq by name:
# run "dnsmasq --help dhcp" to get a list.
# Note that all the common settings, such as netmask and
# broadcast address, DNS server and default route, are given
# sane defaults by dnsmasq. You very likely will not need
# any dhcp-options. If you use Windows clients and Samba, there
# are some options which are recommended, they are detailed at the
# end of this section.

# Override the default route supplied by dnsmasq, which assumes the
# router is the same machine as the one running dnsmasq.

# Do the same thing, but using the option name

# Override the default route supplied by dnsmasq and send no default
# route at all. Note that this only works for the options sent by
# default (1, 3, 6, 12, 28) the same line will send a zero-length option
# for all other option numbers.

# Set the NTP time server addresses to and

# Send DHCPv6 option. Note [] around IPv6 addresses.

# Send DHCPv6 option for namservers as the machine running
# dnsmasq and another.

# Set the NTP time server address to be the same machine as
# is running dnsmasq

# Set the NIS domain name to "welly"

# Set the default time-to-live to 50

# Set the "all subnets are local" flag

# Send the etherboot magic flag and then etherboot options (a string).

# Specify an option which will only be sent to the "red" network
# (see dhcp-range for the declaration of the "red" network)
# Note that the tag: part must precede the option: part.
#dhcp-option = tag:red, option:ntp-server,

# The following DHCP options set up dnsmasq in the same way as is specified
# for the ISC dhcpcd in
# adapted for a typical dnsmasq installation where the host running
# dnsmasq is also the host running samba.
# you may want to uncomment some or all of them if you use
# Windows clients and Samba.
#dhcp-option=19,0           # option ip-forwarding off
#dhcp-option=44,     # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)
#dhcp-option=45,     # netbios datagram distribution server
#dhcp-option=46,8           # netbios node type

# Send an empty WPAD option. This may be REQUIRED to get windows 7 to behave.

# Send RFC-3397 DNS domain search DHCP option. WARNING: Your DHCP client
# probably doesn't support this......

# Send RFC-3442 classless static routes (note the netmask encoding)

# Send vendor-class specific options encapsulated in DHCP option 43.
# The meaning of the options is defined by the vendor-class so
# options are sent only when the client supplied vendor class
# matches the class given here. (A substring match is OK, so "MSFT"
# matches "MSFT" and "MSFT 5.0"). This example sets the
# mtftp address to for PXEClients.

# Send microsoft-specific option to tell windows to release the DHCP lease
# when it shuts down. Note the "i" flag, to tell dnsmasq to send the
# value as a four-byte integer - that's what microsoft wants. See

# Send the Encapsulated-vendor-class ID needed by some configurations of
# Etherboot to allow is to recognise the DHCP server.

# Send options to PXELinux. Note that we need to send the options even
# though they don't appear in the parameter request list, so we need
# to use dhcp-option-force here.
# See for details.
# Magic number - needed before anything else is recognised
# Configuration file name
# Path prefix
# Reboot time. (Note 'i' to send 32-bit value)

# Set the boot filename for netboot/PXE. You will only need
# this is you want to boot machines over the network and you will need
# a TFTP server; either dnsmasq's built in TFTP server or an
# external one. (See below for how to enable the TFTP server.)

# The same as above, but use custom tftp-server instead machine running dnsmasq

# Boot for Etherboot gPXE. The idea is to send two different
# filenames, the first loads gPXE, and the second tells gPXE what to
# load. The dhcp-match sets the gpxe tag for requests from gPXE.
#dhcp-match=set:gpxe,175 # gPXE sends a 175 option.

# Encapsulated options for Etherboot gPXE. All the options are
# encapsulated within option 175
#dhcp-option=encap:175, 1, 5b         # priority code
#dhcp-option=encap:175, 176, 1b       # no-proxydhcp
#dhcp-option=encap:175, 177, string   # bus-id
#dhcp-option=encap:175, 189, 1b       # BIOS drive code
#dhcp-option=encap:175, 190, user     # iSCSI username
#dhcp-option=encap:175, 191, pass     # iSCSI password

# Test for the architecture of a netboot client. PXE clients are
# supposed to send their architecture as option 93. (See RFC 4578)
#dhcp-match=peecees, option:client-arch, 0 #x86-32
#dhcp-match=itanics, option:client-arch, 2 #IA64
#dhcp-match=hammers, option:client-arch, 6 #x86-64
#dhcp-match=mactels, option:client-arch, 7 #EFI x86-64

# Do real PXE, rather than just booting a single file, this is an
# alternative to dhcp-boot.
#pxe-prompt="What system shall I netboot?"
# or with timeout before first available action is taken:
#pxe-prompt="Press F8 for menu.", 60

# Available boot services. for PXE.
#pxe-service=x86PC, "Boot from local disk"

# Loads <tftp-root>/pxelinux.0 from dnsmasq TFTP server.
#pxe-service=x86PC, "Install Linux", pxelinux

# Loads <tftp-root>/pxelinux.0 from TFTP server at
# Beware this fails on old PXE ROMS.
#pxe-service=x86PC, "Install Linux", pxelinux,

# Use bootserver on network, found my multicast or broadcast.
#pxe-service=x86PC, "Install windows from RIS server", 1

# Use bootserver at a known IP address.
#pxe-service=x86PC, "Install windows from RIS server", 1,

# If you have multicast-FTP available,
# information for that can be passed in a similar way using options 1
# to 5. See page 19 of

# Enable dnsmasq's built-in TFTP server

# Set the root directory for files available via FTP.

# Make the TFTP server more secure: with this set, only files owned by
# the user dnsmasq is running as will be send over the net.

# This option stops dnsmasq from negotiating a larger blocksize for TFTP
# transfers. It will slow things down, but may rescue some broken TFTP
# clients.

# Set the boot file name only when the "red" tag is set.

# An example of dhcp-boot with an external TFTP server: the name and IP
# address of the server are given after the filename.
# Can fail with old PXE ROMS. Overridden by --pxe-service.

# If there are multiple external tftp servers having a same name
# (using /etc/hosts) then that name can be specified as the
# tftp_servername (the third option to dhcp-boot) and in that
# case dnsmasq resolves this name and returns the resultant IP
# addresses in round robin fasion. This facility can be used to
# load balance the tftp load among a set of servers.

# Set the limit on DHCP leases, the default is 150

# The DHCP server needs somewhere on disk to keep its lease database.
# This defaults to a sane location, but if you want to change it, use
# the line below.

# Set the DHCP server to authoritative mode. In this mode it will barge in
# and take over the lease for any client which broadcasts on the network,
# whether it has a record of the lease or not. This avoids long timeouts
# when a machine wakes up on a new network. DO NOT enable this if there's
# the slightest chance that you might end up accidentally configuring a DHCP
# server for your campus/company accidentally. The ISC server uses
# the same option, and this URL provides more information:

# Run an executable when a DHCP lease is created or destroyed.
# The arguments sent to the script are "add" or "del",
# then the MAC address, the IP address and finally the hostname
# if there is one.

# Set the cachesize here.

# If you want to disable negative caching, uncomment this.

# Normally responses which come form /etc/hosts and the DHCP lease
# file have Time-To-Live set as zero, which conventionally means
# do not cache further. If you are happy to trade lower load on the
# server for potentially stale date, you can set a time-to-live (in
# seconds) here.

# If you want dnsmasq to detect attempts by Verisign to send queries
# to unregistered .com and .net hosts to its sitefinder service and
# have dnsmasq instead return the correct NXDOMAIN response, uncomment
# this line. You can add similar lines to do the same for other
# registries which have implemented wildcard A records.

# If you want to fix up DNS results from upstream servers, use the
# alias option. This only works for IPv4.
# This alias makes a result of appear as
# and this maps 1.2.3.x to 5.6.7.x
# and this maps> to>

# Change these lines if you want dnsmasq to serve MX records.

# Return an MX record named "" with target
# and preference 50,,50

# Set the default target for MX records created using the localmx option.

# Return an MX record pointing to the mx-target for all local
# machines.

# Return an MX record pointing to itself for all local machines.

# Change the following lines if you want dnsmasq to serve SRV
# records.  These are useful if you want to serve ldap requests for
# Active Directory and other windows-originated DNS requests.
# See RFC 2782.
# You may add multiple srv-host lines.
# The fields are <name>,<target>,<port>,<priority>,<weight>
# If the domain part if missing from the name (so that is just has the
# service and protocol sections) then the domain given by the domain=
# config option is used. (Note that expand-hosts does not need to be
# set for this to work.)

# A SRV record sending LDAP for the domain to
# port 389,,389

# A SRV record sending LDAP for the domain to
# port 389 (using domain=)

# Two SRV records for LDAP, each with different priorities,,389,1,,389,2

# A SRV record indicating that there is no LDAP server for the domain

# The following line shows how to make dnsmasq serve an arbitrary PTR
# record. This is useful for DNS-SD. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for PTR records.)
#ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"

# Change the following lines to enable dnsmasq to serve TXT records.
# These are used for things like SPF and zeroconf. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for TXT records.)

#Example SPF.,"v=spf1 a -all"

#Example zeroconf,name=value,paper=A4

# Provide an alias for a "local" DNS name. Note that this _only_ works
# for targets which are names from DHCP or /etc/hosts. Give host
# "bert" another name, bertrand

# For debugging purposes, log each DNS query as it passes through
# dnsmasq.

# Log lots of extra information about DHCP transactions.

# Include a another lot of configuration options.

And dig gets this response:

Code: Select all
; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> test.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31128
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;test.lan.                      IN      A

.                       1800    IN      SOA 2013091700 1800 900 604800 86400

;; Query time: 77 msec
;; WHEN: Tue Sep 17 11:57:13 2013
;; MSG SIZE  rcvd: 101

I hate being Bi-Polar, It's Awesome!
User avatar
Posts: 7
Joined: 2013-09-13 12:09
Location: Sunderland

Re: Networking Woes

Postby bw123 » 2013-09-17 12:44

have you tried setting domain to just test.lan and then setting test.lan in /etc/hosts?

looks complicated, machine running dnsmasq has address/domain inside dhcp range

if you can't ping, might be a firewall on the router, it's probably easier to setup basic connectivity first, and then dnsmasq and other stuff but I do it backwards a lot of times too,
User avatar
Posts: 2989
Joined: 2011-05-09 06:02
Location: TN_USA

Re: Networking Woes

Postby dilberts_left_nut » 2013-09-17 14:11

figroll wrote:
Code: Select all
;test.lan.                      IN      A

.                       1800    IN      SOA 2013091700 1800 900 604800 86400

;; Query time: 77 msec

Your dig is querying google, not your own server.

Even if it was ...
figroll wrote:
Code: Select all
# Add local-only domains here, queries in these domains are answered
# from /etc/hosts or DHCP only.
you don't have test.lan set as a local domain.

figroll wrote:interface=eth0

Here you have told it to listen on two interfaces, but then restricted it to one IP address.

Also, you have set test.lan to be the domain name appended to hostnames in the specified subnet (which is generally unnecessary unless you have multiple subnets you want to differentiate by name).

If you are expecting test.lan to resolve to a host, where have you set that?
AdrianTM wrote:There's no hacker in my grandma...
User avatar
Posts: 4831
Joined: 2009-10-05 07:54
Location: enzed

Re: Networking Woes

Postby figroll » 2013-09-17 16:37

Thanks for the replies, networking wise I'm new to this thanks for the patience.

So if i remove googles DNS servers that will just query the LAN? (What I want).

I understand if I say set

Code: Select all


Code: Select all

that will resolve test.lan?

how do I (with the setup above) get the dnsmasq to listen to everything that goes through the router to load sites up in windows?

Again thanks :)

*** EDIT ***

I'm now getting a response from dig, it appears Dnsmasq is working better:

Code: Select all
; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> test.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61863
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;test.lan.                 IN      A

test.lan.          0       IN      A

;; Query time: 9 msec
;; WHEN: Tue Sep 17 18:37:25 2013
;; MSG SIZE  rcvd: 47

However if I setup the windows 7 machine to use as an alternate dns server I get no internet! so a bit debugging to do, next to get MX records also....

I hate being Bi-Polar, It's Awesome!
User avatar
Posts: 7
Joined: 2013-09-13 12:09
Location: Sunderland

Return to System configuration

Who is online

Users browsing this forum: No registered users and 4 guests