Geekzone: technology news, blogs, forums
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.

27 posts

+1 received by user: 3

# 35973 17-Jun-2009 21:14
Send private message

Hi there,

I've decided (and set-up) a server at home and am going to be dabbling in doing a bit of hosting and having remote access to my network at home.

So I've got a server setup and running Windows Server 2008, and IIS and everything - this accessible from the current IP on the outside world (using a seperate connection to test this), and I can verify that it is accessible. The ports are all forwarded, yaddah yah...

Now, I've only got a dyamic IP address, and I don't have an option of changing this - I wish I could go static but do not have a choice.

I've messed around with this heaps previously, and have yet again, set up an account with so that I can access the server all the time from a single address. This being - my problem is, that even though this is being updated (as reported by the DYNDNS client on the server) and the fact that I can definately view the server via the current IP on the outside world, the address will not work, even though it responds to pings.

So my question is, what is going on here? Why can I not access it when using the auto-updated dydns domain, but can when I use the IP?

Any help is much, much appreciated, and I hope I've been detailed enough :)

Create new topic
1245 posts

Uber Geek
+1 received by user: 156

  # 225998 17-Jun-2009 22:22
Send private message

Have you done a tracert to see where it's timing out, also when you ping it i'm guessing that it's pinging the correct address?

I run my connection through dnsexit and it's fine, some ISP's cache the DNS results so sometimes when there is an IP change it can take some time (many hours) to update.


198 posts

Master Geek
+1 received by user: 6

  # 226242 18-Jun-2009 12:17
Send private message

what plan are you on that doesn't give you a choice of static IP? unless your on the go-large you can get it on any plan? its $20 a month unless your on a pro plan in which case its free.

either way, nitrotech is right, the way DNS works is there are top tier servers and 2nd teir, 3rd teir blah blah and when a change is made it can take upto 12 hours to propagate right through everyone.

One option is to use a different DNS server, ie, if you use as the dns server on your PC at the remote location then you may find your dynamic dns works a lot better and is updated faster. But of course that will fix your issue but other people accessing your site may not be so lucky which is why you have to be careful with dyndns if its a public site. is one I have used and worked.



8033 posts

Uber Geek
+1 received by user: 390


  # 226469 18-Jun-2009 22:22
Send private message

Have you added the host address to the host header setting for the website in IIS?  If not try that.


923 posts

Ultimate Geek
+1 received by user: 21


  # 226487 18-Jun-2009 22:59
Send private message

kdn: >either way, nitrotech is right, the way DNS works is there are top tier servers and 2nd teir, 3rd teir blah blah and when a change is made it can take upto 12 hours to propagate right through everyone.

Almost. DNS propagation delays are purely related to any given DNS record's TTL, or Time-To-Live. The majority of records in the wild have a TTL of 12 or 24 hours, but it's not uncommon to see up to a week, or as short as 5 minutes.

What happens, is that an initial query by a user causes their DNS server to look up the domain asked for. This starts off by asking the root servers (top tier as you put it) where the TLD is (.com, .org, .nz, etc). These TLD (Top Level Domains) have their own DNS servers, which are then asked where the next domain is ( The next query is to the servers to ask where is. The next query is to ask the servers where is.

This record has a TTL, and what it indicates to the querying server is that it should cache that result for that many seconds, and not bother re-querying until that time has expired. Once it has, the entire query is started over - with exception of any records used to find the ultimate result that haven't themselves expired. (for example, may have a TTL of 48 hours, but only has 2 hours - this means the roots and .nz will not be queried for 48 hours, but will be queried for every 2 hours. Assuming that the querying DNS server is serving a geekzone user with ADD that refreshes the forums_unread.asp page every 2-3 minutes :) )

The above is a pretty general explanation, there's more to it than that. I've not touched on Negative TTL's which are even more confusing.

The last point to mention is that most dyndns servers apply a TTL of 1-5 minutes on their dyndns records.

Here's an example query tree:

$ dig +trace

; > DiG 9.5.1-P1 > +trace
;; global options: printcmd
;; Received 512 bytes from in 17 ms

nz. 172800 IN NS
nz. 172800 IN NS
nz. 172800 IN NS
nz. 172800 IN NS
nz. 172800 IN NS
nz. 172800 IN NS
nz. 172800 IN NS
;; Received 394 bytes from in 12 ms 86400 IN NS 86400 IN NS
;; Received 110 bytes from in 160 ms 3600 IN CNAME 3600 IN A 3600 IN NS 3600 IN NS
;; Received 140 bytes from in 155 ms

(in this instance, .nz servers answered where is, rather than where is - this is because .nz DNS server have every .nz domain, the .nz subdomains are not separated out onto separate servers like some other TLDs)



923 posts

Ultimate Geek
+1 received by user: 21


  # 226488 18-Jun-2009 23:02
Send private message

Oh, I should mention that the TTL's are visible above - the number after the DNS record. is currently set with a TTL of 1 hour (3600 seconds), whereas the records that specify where the GZ DNS servers are have a TTL of 1 day (86400 seconds).


Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:

Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:

Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:

News »

HPE to acquire supercomputing leader Cray
Posted 20-May-2019 11:07

Techweek starting around NZ today
Posted 20-May-2019 09:52

Porirua City Council first to adopt new council software solution Datascape
Posted 15-May-2019 12:00

New survey provides insight into schools' technology challenges and plans
Posted 15-May-2019 09:30

Apple Music now available on Alexa devices in Australia and New Zealand
Posted 15-May-2019 09:11

Make a stand against cyberbullying this Pink Shirt Day
Posted 14-May-2019 20:23

Samsung first TV manufacturer to launch the Apple TV App and Airplay 2
Posted 14-May-2019 20:11

Vodafone New Zealand sold
Posted 14-May-2019 07:25

Kordia boosts cloud performance with locally-hosted Microsoft Azure ExpressRoute
Posted 8-May-2019 10:25

Microsoft Azure ExpressRoute in New Zealand opens up faster, more secure internet for Kiwi businesses
Posted 8-May-2019 09:39

Vocus Communications to deliver Microsoft Azure Cloud Solutions through Azure ExpressRoute
Posted 8-May-2019 09:25

Independent NZ feature film #statusPending to premiere during WLG-X
Posted 6-May-2019 22:13

The ultimate dog photoshoot with Nokia 9 PureView #ForgottenDogsofInstagram
Posted 6-May-2019 09:41

Nokia 9 PureView available in New Zealand
Posted 6-May-2019 09:06

Motorola Solutions joins local partners to deliver advanced communications network in New Zealand
Posted 30-Apr-2019 21:50

Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.

Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.