Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

All .de domains broken

2»

Comments

  • JasonMJasonM Member

    @bobert said: .de domains may experience impairments

    yeah my .de sites were down. their entire DNS failed.

  • bogdbogd Member

    @jsg said:
    Funny serial btw in above denic screenshot. Unless of course that TLD was created in 1778 and there were only minor modifications since then.

    Unix epoch, people.... It's a perfectly valid format for serials, and has the advantage that it is by definition "auto-incrementing" :)

    That particular serial points to May 7th, which is probably when the last change was performed.

  • jsgjsg Member, Resident Benchmarker

    @bogd said:

    @jsg said:
    Funny serial btw in above denic screenshot. Unless of course that TLD was created in 1778 and there were only minor modifications since then.

    Unix epoch, people.... It's a perfectly valid format for serials, and has the advantage that it is by definition "auto-incrementing" :)

    That particular serial points to May 7th, which is probably when the last change was performed.

    So denic even can travel into the future? Amazing.

  • edited May 7

    @jsg said:

    @bogd said:

    @jsg said:
    Funny serial btw in above denic screenshot. Unless of course that TLD was created in 1778 and there were only minor modifications since then.

    Unix epoch, people.... It's a perfectly valid format for serials, and has the advantage that it is by definition "auto-incrementing" :)

    That particular serial points to May 7th, which is probably when the last change was performed.

    So denic even can travel into the future? Amazing.

    Don't worry about this guy. He probably also believes that the internet was invented in the 1960s because thats what they told him. Downright ridiculous.

    @bogd wake up sheeple!!

    Thanked by 1jsg
  • jsgjsg Member, Resident Benchmarker

    @totally_not_banned said:

    @jsg said:

    @bogd said:

    @jsg said:
    Funny serial btw in above denic screenshot. Unless of course that TLD was created in 1778 and there were only minor modifications since then.

    Unix epoch, people.... It's a perfectly valid format for serials, and has the advantage that it is by definition "auto-incrementing" :)

    That particular serial points to May 7th, which is probably when the last change was performed.

    So denic even can travel into the future? Amazing.

    Don't worry about this guy. He probably also believes that the internet was invented in the 1960s because thats what they told him. Downright ridiculous.

    @bogd wake up sheeple!!

    Well, he is right with "perfectly valid format for serials" although it goes against common - and reasonable - professional practice. But then, denic always was and is different (and weird).

    I was more surprised by him not even looking at the relevant dates and also by his "by definition auto-incrementing" nonsense.

    But still, I saw no reason to attack him personally for his opinion. Let's be polite and friendly as long as possible.

  • edited May 7

    @jsg said:
    But then, denic always was and is different (and weird).

    Well, at least they became somewhat usable to private individuals when the EU had their whois data stroke, which negates the general German idea of if you do anything on the internet everyone shall know your home address.

    But still, I saw no reason to attack him personally for his opinion. Let's be polite and friendly as long as possible.

    You are right. I should have controlled myself. It is just sometimes hard to stomach when people distort history and act like packets were never transported by carriage with round trips easily taking 3 to 6 months ;)

    Thanked by 2jsg Saragoldfarb
  • bogdbogd Member
    edited May 10

    @jsg said:
    Well, he is right with "perfectly valid format for serials" although it goes against common - and reasonable - professional practice. But then, denic always was and is different (and weird).

    You are correct about the practice, but (to be fair) the use of dates as serials is not really a standard (RFC1912 is just informational).

    I also prefer the date format for serials, but I have met people who prefer timestamps, and I never had any good argument to use against them :)

    I was more surprised by him not even looking at the relevant dates

    I am not sure what you mean here. When I looked at the serial (just before posting), it was May 7th. And the timestamp at that time pointed to an earlier time on the same day.

    If you are talking about the timestamp in the post I was replying to, that points to May 5th ( 1778020921 is May 5th, 22:42:01 UTC). Since the post was made on May 6th, I still do not see the time travel you mention.

    and also by his "by definition auto-incrementing" nonsense.

    The timestamp format can be beneficial in certain scenarios, where you need to be able to generate a zone file that is guaranteed to have a higher serial, without referencing the existing one. For example, a zone file generated via automation from a template.

    But still, I saw no reason to attack him personally for his opinion. Let's be polite and friendly as long as possible.

    I saw no personal attack. Keep in mind that I am new here, so I might be oblivious (or... immune?) to some more subtle forms of attack :)

    Thanked by 1jsg
  • SaragoldfarbSaragoldfarb Member, Megathread Squad

    @bogd said:

    @jsg said:
    Well, he is right with "perfectly valid format for serials" although it goes against common - and reasonable - professional practice. But then, denic always was and is different (and weird).

    You are correct about the practice, but (to be fair) the use of dates as serials is not really a standard (RFC1912 is just informational).

    I also prefer the date format for serials, but I have met people who prefer timestamps, and I never had any good argument to use against them :)

    I was more surprised by him not even looking at the relevant dates

    I am not sure what you mean here. When I looked at the serial (just before posting), it was May 7th. And the timestamp at that time pointed to an earlier time on the same day.

    If you are talking about the timestamp in the post I was replying to, that points to May 5th ( 1778020921 is May 5th, 22:42:01 UTC). Since the post was made on May 6th, I still do not see the time travel you mention.

    and also by his "by definition auto-incrementing" nonsense.

    The timestamp format can be beneficial in certain scenarios, where you need to be able to generate a zone file that is guaranteed to have a higher serial, without referencing the existing one. For example, a zone file generated via automation from a template.

    But still, I saw no reason to attack him personally for his opinion. Let's be polite and friendly as long as possible.

    I saw no personal attack. Keep in mind that I am new here, so I might be oblivious (or... immune?) to some more subtle forms of attack :)

    Its not just denic, Cloudflare, Google loads of big tech. They dont gaf about RFC1912.

Sign In or Register to comment.