DNS: IP address changes of dynamic DNS-Servers not updated




15 years ago
4 years ago


(Reporter: Ruben Kyczev, Assigned: Blake Ross)


Windows 2000

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1

Surf to a site that is located on an webserver with a Dynamic DNS (e.g.
???.dyndns.org). If the servers IP address has changed while Firebird has not
been closed during the first access to this server, the browser still wants to
connect to the old IP though the DDNS entry has been updated. Seems to be some

Reproducible: Always

Steps to Reproduce:
1. Open a HTML-page form a webserver with a Dynamic DNS through entering the
web-servers DDNS-name
2. Make the server change its IP-Adress (say reconnect if the servers got
dial-up connection)
3. Wait some minutes so that the DDNS-entry is updated to the new IP
4. Try to open another page on the DDNS-server by entering web-servers DDNS-name
5. The webserver is no longer found by firebird though other browsers can connect
Actual Results:  

Expected Results:  
Update DDNS-entry to the new IP

Workaround. Close Firebird and start it again. Now you can get access to the
DDNS-server through entering its ddns-name (new IP is updated).

Comment 1

15 years ago
Maybe bug 151929

Comment 2

15 years ago
Definitely 151929

*** This bug has been marked as a duplicate of 151929 ***
Last Resolved: 15 years ago
Resolution: --- → DUPLICATE

Comment 3

14 years ago
REOPEN: the duped bug was specifically about TTL, not cache lasting forever.
QA Contact: benc
Resolution: DUPLICATE → ---
Summary: IP address changes of dynamic DNS-Servers not updated → DNS: IP address changes of dynamic DNS-Servers not updated
Whiteboard: dupeme
moving to the correct component
Component: General → Networking
Product: Firefox → Browser
Version: unspecified → Trunk
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 15 years ago13 years ago
Resolution: --- → EXPIRED


4 years ago
Whiteboard: dupeme
You need to log in before you can comment on or make changes to this bug.