4. TinyDNS Configuration

TinyDNS Configuration

  • L

    Hello,
    I have what I hope will be a straight forward TinyDNS configuration.  I'm coming from Simple DNS Plus on Windows (hardware failure) and figured I'd try to consolidate things by using TinyDNS on pfsense.  However, I'm concerned that I've got a few of the configuration details confused.  Before I turn it on I was hoping someone could take a quick peek and answer some questions.

    I've got two domains that I'd like to add, in Simple DNS Plus land the configuration files look like this:

    ;$; Updated with Simple DNS Plus Record Editor module v. 5.2.120.0 at 01 Nov 2012 11:17:13 -0700
; Zone created with Simple DNS Plus Quick Domain Wizard at 2005-07-13 22:00:32
;$AllowZT 69.72.158.226 75.125.10.187 204.42.254.5 216.117.186.93
;$MinimumTTL 0
$TTL 3600
@	86400	IN SOA	( ns1.curvedline.net. ; Primary DNS server
			  hostmaster.curvedline.net. ; Responsible person
			  2012110101   ; Serial number
			  86400        ; Refresh
			  3600         ; Retry
			  777600       ; Expire
			  3600       ) ; Minimum TTL
		A	75.144.20.57
		NS	free1.dollardns.net.
		NS	puck.nether.net.
		NS	ns2.zoneedit.com.
		NS	ns8.zoneedit.com.
		NS	ns1.curvedline.net.
www		A	75.144.20.57

    ;$; Updated with Simple DNS Plus Record Editor module v. 5.2.121.0 at 31 Dec 2012 03:55:56 -0800
; Zone created with Simple DNS Plus Quick Domain Wizard at 2005-07-13 22:11:09
;$AllowZT 204.42.254.5 216.117.186.93 216.122.7.155 216.227.210.9
;$MinimumTTL 0
$TTL 60
@	86400	IN SOA	( ns1.curvedline.net. ; Primary DNS server
			  hostmaster.curvedline.net. ; Responsible person
			  2012123101   ; Serial number
			  86400        ; Refresh
			  60           ; Retry
			  777600       ; Expire
			  60         ) ; Minimum TTL
		NS	ns7.zoneedit.com. ;ns15.zoneedit.com
		NS	ns1.curvedline.net.
		NS	puck.nether.net.
		NS	free1.dollardns.net.
		NS	ns15.zoneedit.com.
		MX	1 aspmx.l.google.com.
		MX	10 aspmx2.googlemail.com.
		MX	10 aspmx5.googlemail.com.
		MX	10 aspmx3.googlemail.com.
		MX	10 aspmx4.googlemail.com.
		MX	5 alt1.aspmx.l.google.com.
		MX	5 alt2.aspmx.l.google.com.
		TXT	"v=spf1 include:aspmx.googlemail.com ~all"
calendar		CNAME	ghs.google.com.
mail		CNAME	ghs.google.com.
www		A	75.144.20.57

    In TinyDNS, it appears the I'll have to add all the records into the same page instead of using two groups like I was used to in Simple DNS Plus.  If that's the case, should I use a FQDN for all record names?  For the MX records I've always left this field blank (or used @), how should these be added to TinyDNS?

    Here's what my TinyDNS config looks like right now:

    		 <tinydns><config><ipaddress>127.0.0.1</ipaddress>
				 <enableforwarding><interface>wan</interface>
				 <dnscache_listen><regdhcpstatic><regdhcp><enableipmonitoring><refreshinterval><syncxmlrpc><row><ztipaddress>69.72.158.226</ztipaddress>
					<dnszone>*</dnszone></row> 
				 <row><ztipaddress>75.125.10.187</ztipaddress>
					<dnszone>*</dnszone></row> 
				 <row><ztipaddress>216.117.186.93</ztipaddress>
					<dnszone>*</dnszone></row> 
				 <row><ztipaddress>216.122.7.155</ztipaddress>
					<dnszone>*</dnszone></row> 
				 <row><ztipaddress>216.227.210.9</ztipaddress>
					<dnszone>*</dnszone></row></syncxmlrpc></refreshinterval></enableipmonitoring></regdhcp></regdhcpstatic></dnscache_listen></enableforwarding></config></tinydns> 
		 <tinydnsdomains><config><hostname>curvedline.net</hostname>
				<recordtype>SOA</recordtype>
				<ipaddress>ns.curvedline.net.</ipaddress>
				<ttl>60</ttl>
				 <dist><srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></dist></config> 
			 <config><hostname>www</hostname>
				<recordtype>A</recordtype>
				<ipaddress>75.144.20.57</ipaddress>
				 <ttl><dist><srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></dist></ttl></config> 
			 <config><hostname>calendar</hostname>
				<recordtype>CNAME</recordtype>
				<ipaddress>ghs.google.com</ipaddress>
				 <ttl><dist><srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></dist></ttl></config> 
			 <config><hostname>@</hostname>
				<recordtype>MX</recordtype>
				<ipaddress>aspmx.l.google.com</ipaddress>
				<ttl>300</ttl>
				<dist>1</dist>
				 <srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></config> 
			 <config><hostname>@</hostname>
				<recordtype>MX</recordtype>
				<ipaddress>aspmx2.googlemail.com</ipaddress>
				<ttl>300</ttl>
				<dist>10</dist>
				 <srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></config> 
			 <config><hostname>@</hostname>
				<recordtype>MX</recordtype>
				<ipaddress>aspmx3.googlemail.com</ipaddress>
				<ttl>300</ttl>
				<dist>10</dist>
				 <srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></config> 
			 <config><hostname>@</hostname>
				<recordtype>MX</recordtype>
				<ipaddress>alt1.aspmx.l.google.com</ipaddress>
				<ttl>300</ttl>
				<dist>5</dist>
				 <srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></config> 
			 <config><hostname>@</hostname>
				<recordtype>MX</recordtype>
				<ipaddress>alt2.aspmx.l.google.com</ipaddress>
				<ttl>300</ttl>
				<dist>5</dist>
				 <srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></config> 
			 <config><hostname>@</hostname>
				<recordtype>TXT</recordtype>
				<ipaddress>v=spf1 include:aspmx.googlemail.com ~all</ipaddress>
				 <ttl><dist><srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></dist></ttl></config> 
			 <config><hostname>ffljam.com</hostname>
				<recordtype>SOA</recordtype>
				<ipaddress>ns.curvedline.net.</ipaddress>
				<ttl>300</ttl>
				 <dist><srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></dist></config> 
			 <config><hostname>www.ffljam.com</hostname>
				<recordtype>A</recordtype>
				<ipaddress>75.144.20.57</ipaddress>
				<ttl>300</ttl>
				 <dist><srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></dist></config> 
			 <config><hostname>ns.curvedline.net</hostname>
				<recordtype>NS</recordtype>
				<ipaddress>75.144.20.57</ipaddress>
				<ttl>300</ttl>
				 <dist><srv_port><srv_priority><srv_weight><srv_timestamp><rdns><monitorip><threshhold></threshhold></monitorip></rdns></srv_timestamp></srv_weight></srv_priority></srv_port></dist></config></tinydnsdomains>

    Am I on the right path?  Are there entries that I'm missing?  Any help would be appreciated.

    Thanks,
    Chris

    Ps.  I've tried looking for tutorials but most questions appear to be about internal dns resolution.  I'm using the DNS forwarder for that and just want TinyDNS for external use.

    0
  • L

    I forgot to mention, while I haven't setup a NAT rule to point to TinyDNS, I do have the server enabled.  However, when I look at the logs tab I see the following error:

    CSRF check failed. Either your session has expired, this page has been inactive too long, or you need to enable cookies.
    Debug:

    Could this be related to the Perl mismatch issue I'm also having with LightSquid (500 - Internal Server Error)?

    0
Log in to reply
 

Products

Applications

Support

Services

News

Resources

Company

Our Mission

As host of the pfSense open source firewall project, Netgate believes in enhancing network connectivity that maintains both security and privacy. We also believe everyone should be able to afford it.

Subscribe to our Newsletter

Product information, software announcements, and special offers. See our newsletter archive for past announcements.

© Copyright 2002 - 2019 Rubicon Communications, LLC | Privacy Policy