File: tests-ietf.org.patch

package info (click to toggle)
py3dns 4.0.2-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 360 kB
  • sloc: python: 1,984; makefile: 10; sh: 7
file content (33 lines) | stat: -rw-r--r-- 1,467 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
From: Colin Watson <cjwatson@debian.org>
Date: Sun, 13 Jul 2025 17:25:44 +0200
Subject: Handle changed MX records for ietf.org

Forwarded: https://code.launchpad.net/~cjwatson/py3dns/+git/py3dns/+merge/488798
Bug-Debian: https://bugs.debian.org/1108799
Last-Update: 2025-07-13
---
 DNS/tests/test_base.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/DNS/tests/test_base.py b/DNS/tests/test_base.py
index 763ec07..fe3e72f 100644
--- a/DNS/tests/test_base.py
+++ b/DNS/tests/test_base.py
@@ -93,7 +93,7 @@ class TestBase(unittest.TestCase):
         self.assertTrue(mx_response.answers[0])
         # is hard coding a remote address a good idea?
         # I think it's unavoidable. - sk
-        self.assertEqual(mx_response.answers[0]['data'], (0, 'mail.ietf.org'))
+        self.assertEqual(mx_response.answers[0]['data'], (0, 'mail2.ietf.org'))
 
         m = DNS.mxlookup('ietf.org', timeout=1)
         self.assertEqual(mx_response.answers[0]['data'], m[0])
@@ -193,7 +193,7 @@ class TestBase(unittest.TestCase):
         self.assertTrue(mx_response.answers[0])
         # is hard coding a remote address a good idea?
         # I think it's unavoidable. - sk
-        self.assertEqual(mx_response.answers[0]['data'], (0, 'mail.ietf.org'))
+        self.assertEqual(mx_response.answers[0]['data'], (0, 'mail2.ietf.org'))
 
         m = DNS.mxlookup('ietf.org', timeout=1)
         self.assertEqual(mx_response.answers[0]['data'], m[0])